release/1.5.0: Bug fix for spack stack setup-meta-modules extension when no Python is built/used #323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… Python after checking with user
climbfuji
force-pushed
the
bugfix/meta_modules_no_python
branch
from
b4b475a
to
1fb4b58
Compare
climbfuji
changed the title
climbfuji
requested review from
srherbener,
ulmononian and
AlexanderRichert-NOAA
AlexanderRichert-NOAA
approved these changes
Sep 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This bug fix for the
spack stack setup-meta-modulesextension allows the user to proceed when no Python is built/used. This is becoming relevant for us when using spack environment chaining for testing/installing new packages for the UFS, for example.Tested on my macOS.
Issue(s) addressed
n/a
Dependencies
n/a
Impact
n/a
Checklist
I have made corresponding changes to the documentation