add restriction to py-setuptools dependency on py-flake8#6589
Merged
junghans merged 1 commit intospack:developfrom Dec 8, 2017
Merged
add restriction to py-setuptools dependency on py-flake8#6589junghans merged 1 commit intospack:developfrom
junghans merged 1 commit intospack:developfrom
Conversation
3 tasks
junghans
approved these changes
Dec 8, 2017
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note: This exposes a compatibility issue with
py-ipythonwhich depends onpy-backports-shutil-get-terminal-sizewhich depends (as build dependency only) onpy-setuptools:30.99.99.Currently it is not possible to concretize a spec that has conflicting build and run dependencies. All other packages (in all of spack) depend on
[email protected]:so I'm not sure if that adds to much pressure on a concretizer that is able to handle such cases, but for our meta-package it results in a brokenpy-flake8build and after this is merged will result in a failure to concretize.Is there an estimate on when the new concretizer will be implemented? @scheibelp @tgamblin @adamjstewart