Skip to content

[3.9] bpo-43077: Update bundled pip to 21.0.1 and setuptools to 52.0.0 (GH-24386) #24387

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

Closed
wants to merge 1 commit into from

Conversation

pfmoore
Copy link
Member

@pfmoore pfmoore commented Jan 30, 2021

Update bundled pip to 21.0.1 and setuptools to 52.0.0.
(cherry picked from commit 4d11ecb)

Co-authored-by: Paul Moore [email protected]

https://bugs.python.org/issue43077

pythonGH-24386)

Update bundled pip to 21.0.1 and setuptools to 52.0.0.
(cherry picked from commit 4d11ecb)

Co-authored-by: Paul Moore <[email protected]>
@pfmoore
Copy link
Member Author

pfmoore commented Jan 30, 2021

:-( Looks like ensurepip changed between 3.9 and 3.10, probably to handle the fact that we're no longer shipping py2.py3 wheels. I'll look at backporting that fix and hopefully that will address this.


_PIP_VERSION = "20.2.3"

_PACKAGE_NAMES = ('setuptools', 'pip')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this being set

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR didn't backport cleanly, and I had to manually fix the merge conflict. I didn't notice that this variable isn't used in the older version of the code. It's harmless, but can be fixed. It's not the cause of the test failures, sadly.

@pfmoore
Copy link
Member Author

pfmoore commented Jan 30, 2021

Test failures seem to be coming from a deprecation warning for a "legacy version" where the version being parsed is "pip". I have no clue why that's happening, but modifying the test (test.test_venv, line 450) to not treat warnings as errors causes the test to pass.

My tentative assumption is that something in the code has been incorrectly parsing "pip" as a version for some time, but it's been harmless until now. With legacy versions now being warned about, that causes the test to fail with a hard error here.

The bad news is I have no idea what is causing the code to try to parse "pip" as if it were a version. It's almost impossible to instrument the code, because it's being run directly from the wheel, and if I modify the code I'll need to regenerate RECORD, etc...

I don't have time right now to debug this much further. @pradyunsg if you have any insights, I'd be very grateful!

@pfmoore
Copy link
Member Author

pfmoore commented Jan 30, 2021

pypa/pip#9540

@github-actions
Copy link

github-actions bot commented Mar 2, 2021

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Mar 2, 2021
@sbidoul
Copy link
Contributor

sbidoul commented Apr 24, 2021

Superseded by #25578

@matrixise
Copy link
Member

Hi @pfmoore

I close this PR because it is superseded by #25578.

Thank you so much for your PR.

@matrixise matrixise closed this Apr 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting core review stale Stale PR or inactive for long period of time.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants