Skip to content
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

default python preference for packages.yaml #11539

Closed
wants to merge 1 commit into from

Conversation

baberlevi
Copy link
Member

This PR adds a python preference order to default packages.yaml to help with issues relating to python2/3 concretization errors.

This doesn't solve all issues related to the 2/3 difficulty, but I think would make the 'out of the box' experience work more as expected without user customization required, especially for setups like environments and building in containers.

Related to: #11531, #11468, #11396

@adamjstewart
Copy link
Member

Spack packages always default to the newest stable release. In the case of python, we explicitly set the default to 2 instead of 3. If we want to change the default to Python 3, this should be done by removing preferred=True, not by overriding the default in packages.yaml. See #10319 for the correct way to do this. Unfortunately, not all packages work with Python 3, and solving your concretization bugs will introduce bugs for others. Until #11468 is worked out, we won't be able to merge #10319.

@baberlevi
Copy link
Member Author

Makes sense - thanks for the explanation & pointer to the other issues

danlipsa added a commit to danlipsa/spack that referenced this pull request Jun 7, 2019
Workaround for
adding the following to your packages.yaml
packages:
  python:
    version: [3, 2]
without this you'll get:
paraview requires python version 3:, but spec asked for 2.7.16
for `spack spec paraview+python`
see spack pull request spack#11539
danlipsa added a commit to danlipsa/spack that referenced this pull request Jun 7, 2019
Workaround for
adding the following to your packages.yaml
packages:
  python:
    version: [3, 2]
without this you'll get:
paraview requires python version 3:, but spec asked for 2.7.16
for `spack spec paraview+python`
see spack pull request spack#11539
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants