Skip to content

Conversation

@Flamefire
Copy link
Contributor

This results in a top-level Python package called "test". As this isn't namespaced to easybuild it can cause issues with other Python packages and shouldn't be installed.

Additionally IMO it isn't useful to install the tests in the first place.

@boegel boegel added the change label Dec 13, 2025
@boegel boegel added this to the 5.x milestone Dec 13, 2025
@boegel boegel changed the title Don't install test package Don't install test.framework package Dec 13, 2025
This results in a top-level Python package called "test".
As this isn't namespaced to easybuild it can cause issues with other
Python packages and shouldn't be installed.
When we no longer install the test package AND want to run outside the
source tree (to test the installed easybuild package) we need to
retrieve the test package first.
We need to use `$PYTHONPATH` instead of `topdir` to include the
framework package in the GC3Pie test.
When testing copies of framework files we need to handle the case where
some might not be available and try hard to find the source dir.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants