 |
 |
As reported by @nikoladze in #1377 :
However, the case where i originally found the issue was installing in a virtual environment. I didn't know this would make a difference, but apparently this is still a problem:
$ docker run --rm -it python:3.8-buster bash
$ apt-get update && apt-get -y install cmake
$ python3 -m venv test-venv
$ source test-venv/bin/activate
$ pip install wheel
$ pip install --index-url https://test.pypi.org/simple/ xrootd==7.7.20
$ python
>>> import pyxrootd.client
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'pyxrootd.client'
The client.<something>.so file seems missing:
$ ls /test-venv/lib/python3.8/site-packages/pyxrootd/
include lib share
For comparison when installing globally (not in venv) the folder looks like this:
$ ls /usr/local/lib/python3.8/site-packages/pyxrootd
_init__.py __pycache__ client.cpython-38-x86_64-linux-gnu.so include lib share
Also, the XRootD module folder is missing when installing in the venv.
It is maybe worth noting that during installation pip tries to install via "wheel" and then falls back to setup.py install. In newer versions there is this warning: "DEPRECATION: Could not build wheels for xrootd which do not use PEP 517. pip will fall back to legacy 'setup.py install' for these. pip 21.0 will remove support for this functionality."
I don't really know much about the different ways to make python packages, but maybe this should be kept in mind since it sounds like it could break the package again in the future.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1