Skip to content

paraview: Adjust python version constraints#13999

Merged
adamjstewart merged 1 commit intospack:developfrom
chuckatkins:drop-py-matplotlib-version-constraint
Dec 5, 2019
Merged

paraview: Adjust python version constraints#13999
adamjstewart merged 1 commit intospack:developfrom
chuckatkins:drop-py-matplotlib-version-constraint

Conversation

@chuckatkins
Copy link
Copy Markdown

@chuckatkins chuckatkins commented Dec 5, 2019

  • py-matplotlib: No constraint necessary for py3 but py2 has an upper bound
  • py-numpy: No constraint necessary for py3 but py2 has an upper bound

Related to #13985

py-matplotlib: No constraint necessary for py3 but py2 has an upper bound
py-numpy: No constraint necessary for py3 but py2 has an upper bound
@chuckatkins chuckatkins force-pushed the drop-py-matplotlib-version-constraint branch from 848a6a4 to 291ce0f Compare December 5, 2019 15:48
@chuckatkins chuckatkins changed the title paraview: Drop artificial version constraint on py-matplotlib paraview: Adjust python version constraints Dec 5, 2019
@adamjstewart
Copy link
Copy Markdown
Member

Now that Spack defaults to Python 3 can we finally drop the +python3 variant?

@chuckatkins
Copy link
Copy Markdown
Author

We still need two separate variants, else the concretizer will fail to correctly resolve dependencies. I'm okay with changing the python and python3 variants to python2 and python respectively though. But I believe it's outside the scope of and orthogonal to this PR. I'm happy to follow up separately with it.

@adamjstewart
Copy link
Copy Markdown
Member

Let's wait for the new concretizer then.

@adamjstewart adamjstewart merged commit 831133a into spack:develop Dec 5, 2019
@chuckatkins chuckatkins deleted the drop-py-matplotlib-version-constraint branch December 5, 2019 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants