[ https://issues.apache.org/jira/browse/PROTON-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542585#comment-17542585 ]
Kim van der Riet commented on PROTON-2550: ------------------------------------------ I did a check on what happens if the install is used without the *{{--prefix}}* option. In this case, the identical directory structure is created in {*}{{/usr/local/lib64}}{*}. And with no *{{PYTHONPATH}}* set, python finds the proton module ok: {noformat} $ unset PYTHONPATH $ cd python/dist/ $ python setup.py install # Tried non-root install first ... The following error occurred while trying to add or remove files in the installation directory: [Errno 13] Permission denied: '/usr/local/lib64/python3.10' ... $ sudo python setup.py install ... $ ll /usr/local/lib64/python3.10/site-packages/ total 8 -rw-r--r--. 1 root root 57 May 26 12:36 easy-install.pth drwxr-xr-x. 5 root root 4096 May 26 12:36 python_qpid_proton-0.38.0.dev0-py3.10-linux-x86_64.egg $ cd ~ # Exit from dist directory which contains python install artifacts $ python >>> import proton >>> proton.__path__ ['/usr/local/lib64/python3.10/site-packages/python_qpid_proton-0.38.0.dev0-py3.10-linux-x86_64.egg/proton'] >>> {noformat} So it seems that a local install does not work with a PYTHONPATH set, but with system install which uses the same directory structure in a system location, python finds the proton directory within the .egg directory. What are we missing? How do we make local installs work? > [python-binding] setup.py install does not create module directory when using > --prefix > -------------------------------------------------------------------------------------- > > Key: PROTON-2550 > URL: https://issues.apache.org/jira/browse/PROTON-2550 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding > Reporter: Kim van der Riet > Assignee: Andrew Stitcher > Priority: Major > > After building proton, installing the python bindings using the generated > *{{setup.py}}* does not create all of the necessary directories when used > with the *{{--prefix}}* option. In particular, a directory using the module > name *{{proton}}* is missing. > The following install command from the cmake build directory: > {noformat} > $ export PYTHONPATH=/tmp/lib64/python3.10/site-packages > $ cd python/dist/ > $ python setup.py install --prefix /tmp > $ ls -l /tmp/lib64/python3.10/site-packages/ > total 3 > -rw-rw-r--. 1 kvdr kvdr 57 May 26 11:58 easy-install.pth > drwxrwxr-x. 5 kvdr kvdr 160 May 26 11:58 > python_qpid_proton-0.38.0.dev0-py3.10-linux-x86_64.egg > {noformat} > produces a single {{python_qpid_proton-0.38.0.dev0-py3.10-linux-x86_64.egg}} > directory (and a {{easy-install.pth}} file if the {{PYTHONPATH}} is set prior > to the install). > This is insufficient to use module proton, even with the PYTHONPATH set: > {noformat} > $ cd ~ # Exit from dist directory which contains python install artifacts > $ echo $PYTHONPATH > /tmp/lib64/python3.10/site-packages > $ python > >>> import proton > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ModuleNotFoundError: No module named 'proton' > >>> > {noformat} > However, a workaround exists by adding a symbolic link *{{proton}}* pointing > to the .egg directory: > {noformat} > $ cd /tmp/lib64/python3.10/site-packages/ > $ ln -s python_qpid_proton-0.38.0.dev0-py3.10-linux-x86_64.egg proton > $ cd ~ # Exit from dist directory which contains python install artifacts > $ python > >>> import proton > >>> proton.__path__ > _NamespacePath(['/tmp/lib64/python3.10/site-packages/proton']) > {noformat} -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org