-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Dependency resolver fails when version ranges are specified #9619
Comments
I believe this is the same as #9197 (already fixed, will be in the next release), but will need to double check. |
thanks for the response! |
#9197 is about the |
Closing since this is likely fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What did you want to do?
Attempting to install a package from an internal azure artifact feed (specified either as the only index url or as an extra index url), given a range of acceptable versions (e.g.
>2.6.1
,~=3.0.0
,==3.*
, etc) results in a failure to find a version satisfying the requirement according to pip. Despite, as seen in the output below, finding a number of seemingly qualifying candidates.One thing to note is that all of the candidates for the version ranges I specified are considered release candidates per PEP 440, but testing e.g.:
seems to imply that the versions are valid and should satisfy the criteria.
A possibly related issue---pip was apparently unable to resolve the dependency
click>=6,<7
(output) until specifying the version manually (output). (relevant requirements.txt)Also note that the same issue occurs whether the azure artifact feed is specified as an index or not, i.e.
pip install pros-cli>2.6.1
fails just the same.Is pip just ignoring prereleases for the purposes of dependency resolution? Is there a way to force it to allow them?
`pip freeze`
Output
the command output
The text was updated successfully, but these errors were encountered: