-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python packages might have the wrong version due not using pip #2389
Comments
Wouldn't a better way of verifying which version is installed via |
And in this case this is actually the problem:
I.e. pip finds meta data of 19.2.3 but the actually used package is version 19.0.3 |
@Flamefire I think we can consider this as fixed thanks to #2367 + #2377? |
The issue here wasn't the 0.0 version but the difference shown via So rather easybuilders/easybuild-easyconfigs#12650 was a good step in fixing this and we should get #2127 done, at least for 5.0 |
In e.g.
Python-3.7.4-GCCcore-8.3.0.eb
we install pip without pip which leads to the installation of an egg-file/folder.This doesn't play nice with
pip
in general. E.g.pip list
lists pip as 19.2.3 (as it should be) butpython -c 'import pip; print(pip.__version__)
shows 19.0.3This means that we don't get what we asked for.
In this case it is admittedly quite special because we install a base pip via
ensurepip
(a bundled pip in Python) and then again via setup.py but it shows that using setup.py is unreliable / doesn't work well together with pipHence we should strive VERY hard to avoid any
use_pip: False
or anything whereuse_pip: True
is not set.Additionally it might make sense to check for the case where
python -c 'import <module>; print(<module>.__version__)
prints something else than the expected version and add this as a sanity check.Possible problems:
__version__
may not be defined --> I'd allow the command to failThe text was updated successfully, but these errors were encountered: