-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fixes for the cases that raise Tracebacks in outdated pip version check #5764
Fixes for the cases that raise Tracebacks in outdated pip version check #5764
Conversation
c838698
to
9019ed5
Compare
Any reason to just not cache the check, but otherwise still perform it when the cache is disabled? |
Ah. Oversight. :) I'll see what to do for that. #5680 should be close enough in that case. |
9019ed5
to
692929e
Compare
692929e
to
1e0247f
Compare
Updated the description according to the updated PR. Fixes all the same issues as before. |
CI passes and I am happy with these changes. I'll go ahead and merge this. |
When is the next release due? This is the only issue blocking my team to upgrade pip to 18.x |
@nehaljwani: soon: #5782. |
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. |
Fixes #5679. The
selfcheck.json
file is stored in the cache. If the cache is disabled, this file can not be accessed and so pip shouldn't cache the version in that case.Fixes #5433 (and closes #5680). Instead of performing the version check for every command, only perform the check with commands have the required (index) options.