-
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
update easyblock to let EasyBuild framework take care of prepend to $PYTHONPATH
or $EBPYTHONPREFIXES
+ make PythonBundle
and PythonPackage
aware of --prefer-python-search-path
EasyBuild configuration option
#3343
Conversation
prefer_ebpythonprefixes
flag to use EBPYTHONPREFIXES
special easyblocks that have been directly modified:
PythonPackage or PythonBundle or subclasses indirectly modified:
Nothing to test:
(todo: make list of specific easyconfigs to test for the generic easyblocks) |
Slight issue with libxml2; the easyblock inherits from PythonPackage, and PythonPackage has always unconditionally added PYTHONPATH/EBPYTHONPREFIXES, so that behavior is retained here. I could change this; always let the framework add the environment variable if it detects the corresponding path, but this is not done here (yet?) |
2ed73d5
to
1a4bd52
Compare
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 7 out of 7 (7 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 5 out of 5 (5 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 7 out of 7 (7 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 7 out of 7 (7 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) |
Test report by @Micket Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
All the tests above ran fine and produced the correct PYTHONPATH. |
a663110
to
4ba7735
Compare
Some of them looked incorrect as they never actually support EBPYTHONPREFIXES and multi_deps. Relying on the default framework implement instead.
cfa953c
to
e4f8a31
Compare
…ONPATH vs $EBPYTHONPREFIXES in PythonBundle + PythonPackage easyblocks
don't use `force_pythonpath` + clarify why we're keeping logic on `$PYTHONPATH` vs `$EBPYTHONPREFIXES` in `PythonBundle` + `PythonPackage` easyblocks
prefer_ebpythonprefixes
flag to use EBPYTHONPREFIXES$PYTHONPATH
or $EBPYTHONPREFIXES
+ make PythonBundle
and PythonPackage
aware of prefer_python_search-path
$PYTHONPATH
or $EBPYTHONPREFIXES
+ make PythonBundle
and PythonPackage
aware of prefer_python_search-path
$PYTHONPATH
or $EBPYTHONPREFIXES
+ make PythonBundle
and PythonPackage
aware of --prefer-python-search-path
EasyBuild configuration option
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 8 out of 9 (9 easyconfigs in total) |
The failure with the |
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) edit: using standard configuration, so using |
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (2 easyconfigs in total) edit: using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Depends on
$PYTHONPATH
or$EBPYTHONPREFIXES
in generated module files by automatically scanning for python site package directories easybuild-framework#4539Untested.