Closed ccoulombe closed 7 months ago
I suggest setting
exts_default_options['use_pip'] = True
exts_default_options['use_pip_for_deps'] = True
exts_default_options['sanity_pip_check'] = True
if there are Python extensions
Or maybe add a sanity check that there are no .egg
files in the install dir ?
Testing for use_pip in all extensions is not trivial.
I'd prefer to raise an error (like we do with CMake). Plus, these will be defaults in the next EB version
Plus, these will be defaults in the next EB version
which won't raise an error
To accompany https://github.com/ComputeCanada/software-stack/issues/137, and prevent future oopsies, we need to raise an error if a module has a Python extension and uses
python setup.py install
and notpip install
.We then need to update the recipe to use:
and fix/update any issues with the installed python packages.