-
Notifications
You must be signed in to change notification settings - Fork 14
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
pipgrip selects yanked verison #118
Comments
Hi @tekumara 👋 Thanks for the report. It looks like this is an upstream bug. Somehow this output includes the yanked version:
|
Yep, it was reported upstream: pypa/pip#11745 |
Oh interesting, thanks for looking into this. One slight difference i've noticed is that |
Yeah, that's expected behaviour if the yanked versions show up in the |
I opened a PR to fix it: pypa/pip#12225 |
Upstream fix is merged. Thanks for the report! |
What you were trying to do (and why)
pipgrip prefect
will select 2.82 which has been yanked.What happened (including command output)
Command output
What you expected to happen
Yanked versions are ignored
Step-by-step reproduction instructions
pipgrip==0.10.7
The text was updated successfully, but these errors were encountered: