The recent proton-c 0.38.0 release contains significant changes to the way that the python bindings to the proton library build and install. They are now more consistent with the usual packaging standards in the python community:
- The build process will now build a python source package compatible with PyPI and pip install, this will be found in the python/pkgs subdirectory of the build directory. - The build install target by default will not copy any python files to the install prefix leaving you to install to the active python installation using a command like: pip install python/pkgs/python/pkgs/python-qpid-proton-0.38.0.tar.gz > - This command line assumes you are in the build directory and that you have pip installed for use directly - During the python binding install the process tries to find the qpid-proton-core c library using pkgconfig. If it can find the library then it will use the found c library as the base for the installed python binding; if it cannot find the proton core c library then it will build the c library using sources bundled into the python source package. So if you specifically want to use an external proton core C library, you should make sure to install the proton core library first and make sure that pkgconfig can find the library - using the PKG_CONFIG_PATH environment variable may help here. A source package for python-qpid-proton 0.38.0 has been uploaded to PyPI and this can be installed by using: > pip install python-qpid-proton > Installing this package can also give you a bundled or and external proton core library as detailed above. This package is compatible with python virtual environments and this is my recommended way to use them to ensure that the package dependencies are contained and easily manageable. Any comments, questions, etc. very welcome. Andrew
