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
Remove bundled setuptools #95299
Comments
@pablogsal do you think it is still acceptable to do this in 3.11? If positive we can likely land a PR on time for RC1. |
Unfortunately I don't feel comfortable landing this so late in the release cycle, specially so close to RC1 and given the current stability of 3.11 :( This will need to wait until 3.12. |
It feels strange that |
I've filed #101039 for this (almost had a number with three 0s), targetting 3.12. |
Feature or enhancement
Remove the bundled setuptools so that
ensurepip
andpython -m venv
only installs pip.Context
The
setup.py install
command ofsetuptools
is deprecated.However, in an environment where
setuptools
is installed butwheel
is not (such as one created withpython -m venv
), pip falls back on running the deprecated and non-standardsetup.py install
.Since version 22.1 pip works correctly by default in environments where
setuptools
is not installed, by enabling its PEP 517 mode automatically, leading to unsurprising installations in most cases.So, in order to progressively expose more users to standard-based installation workflows, we (the pip team) would like that virtual environments are created without
setuptools
by default.Users faced with failing installations following this change (likely due to packages with customized
setup.py
that do not support building a wheel) can easilypip install setuptools
to solve the issue.Previous discussion
pypa/pip#8102 (comment) and following comments has some more context.
Linked PRs
The text was updated successfully, but these errors were encountered: