-
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
Fix PackageFinder to respect allow_all_prereleases #5927
Conversation
Add test and news file
You broke this use case: $ cp tests/data/packages/simplewheel-1.0-py2.py3-none-any.whl index/foo-1.0-py2.py3-none-any.whl
$ cp tests/data/packages/simplewheel-1.0-py2.py3-none-any.whl index/foo-1.0b1-py2.py3-none-any.whl
$ python src/pip download --no-deps -f index 'foo>=2.0b1'
Looking in links: index
Collecting foo>=1.0
Saved ./foo-1.0-py2.py3-none-any.whl
Successfully downloaded foo
# Instead of:
$ git checkout master
$ python src/pip download --no-deps -f index 'foo>=2.0b1'
Looking in links: index
Collecting foo>=2.0b1
Saved ./foo-2.0b1-py2.py3-none-any.whl
Successfully downloaded fo As evidenced by the fact that you had to patch |
I misunderstood the meaning of that test; will follow up |
OK, I had made a mess of the test... The point is: when using a requirement with a version specifiers using a pre-release, then pre-releases should be allowed (same as if |
I opened #5928 and suggest to close this one |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fix 'PackageFinder.find_all_candidates' to respect 'allow_all_prereleases'
Closes #5175