-
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
Pin the major version of pip to 20 in Python 2 #24636
Comments
At this point we're hoping to be Py3-first by Jan 2021, but we will likely have a few Py2 bots (infra/ tests, some unittests) to help with backwards compatibility, which will still have to be pinned. Leaving this roadmap, because we'll want a reminder before the end of the year to get this done! :) |
Here's the reminder before the year is over! Who should be assigned to this? |
cc @jgraham @gsnedders as folks who might want to know - based on pypa/pip#9282 (comment) this will break in the very last week of us being Py2-compatible (pip is aiming to release on Jan 23/24). I'm very tempted to declare we're moving the py3-only shift forward by a week... |
I think I'm happy with spending the time to move stuff over to Py 3 where required rather than pinning pip. |
|
I'm going to say we can close this now. |
I noticed that pip would drop support for Python 2 starting from v21: pypa/pip#6148
We've been seeing the deprecation warnings when running
wpt run
without--py3
:The timeline seems to be January 2021. And we need to pin the version of pip everywhere we run Python 2 (including the
wpt
frontend and varioustox
tests).The text was updated successfully, but these errors were encountered: