PYTHONPATHs not set for python components after releases/v0.20 #42433
Unanswered
jgalarowicz
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I tried to use spack releases instead of the development branch to build survey in hopes of figuring out why we don't get the PYTHONPATH statements in the survey module file.
I'm asking spack not to load the module files for all the components by using autoload: none feature.
When building survey with spack releases/v0.20, spack puts all the PYTHONPATH statements into the module file for survey. Releases after v0.20 do not put the PYTHONPATH statements in.
I would like to know how we can get this functionality back.
With releases/v0.21 and above we only get the PYTHONPATH for survey, but not the components.
When we try to execute survey we get python module not found error messages.
This is from releases/v0.20 generated spack survey module file:
Thanks,
Jim G
Beta Was this translation helpful? Give feedback.
All reactions