Spack: Python3 #278
Merged
Spack: Python3 #278
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
mainline spack sadly defaults to python2. So let's tell propose python3 to the user by default. We could also increase our requirement in the package, but we do indeed (inofficially) even run with python2.
|
I could not agree more. |
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.
Mainline spack sadly defaults to python2. So let's explicitly tell users how to use python3 by default.
We could also increase our requirement in the package, but we do indeed (unofficially) even run with python2. Nevertheless, our official support is for Python 3, so let's install it by default as such.
Spack usage reference: https://spack.readthedocs.io/en/latest/features.html#customize-dependencies
Thx to @ritiek for the report!