You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some Python packages with own easyblocks, such as numpy, we may want to use pip starting at a specific version, i.e. set use_pip = True. However the required self.version isn't available until __init__ of EasyBlock finishes, so the derived easyblock must call that first. This however results in PythonPackage setting a lot of member variables already, especially it changes EC variables. Some only work for pip or setup.py:
The init method of PythonPackage does a lot depending on EC params
For some Python packages with own easyblocks, such as numpy, we may want to use pip starting at a specific version, i.e. set
use_pip = True
. However the requiredself.version
isn't available until__init__
of EasyBlock finishes, so the derived easyblock must call that first. This however results in PythonPackage setting a lot of member variables already, especially it changes EC variables. Some only work for pip or setup.py:easybuild-easyblocks/easybuild/easyblocks/generic/pythonpackage.py
Lines 449 to 453 in 9e1cdf2
Hence when the derived EasyBlock wants to/can change
use_pip
the state has already been irreversibly modified.The text was updated successfully, but these errors were encountered: