however if instead of
python3 -m pip install
I dopip3 install
it does work like a charm.Any idea why? (pardon my ignorance if this is a trivial question or expected behaviour)
No worries @simonmichal.
python3 -m pip install dist/xrootd-6.0.0.tar.gz
also puts your cwd on sys.path
and as as things currently stand there is a xrootd.egg-info
there, so pip
"sees" the xrootd.egg-info
and says "I already have a distribution of xrootd
v6.0.0
on PYTHONPATH
so there is nothing to install. So there are two alternatives:
--upgrade
even though you don't have anything installed yetpython3 -m pip install --upgrade ./dist/xrootd-6.0.0.tar.gz
xrootd.egg-info
is off PATH. This is how things are done in CI:though I should maybe update that in the future to approach 1 which is easier to understand I think.
Directly calling pip3
doesn't have this behavior as you're not invoking it as a Python module, but then you're not guaranteed to have the right Python do the installation. Here though of course there is only one Python so there is no issue.
You also don't show enabling devtoolset-7
as you're on CentOS 7
but seems you didn't need it?
This (avoiding PATH issues) is one of the reasons that src
distribution layouts for Python packages exist, but that's a discussion for another Issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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