You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some point, docs/Hacking.md so that it doesn’t tell users to upgrade setuptools. We could do it after Python 3.10 has reached end of life, or we could do it sooner with a note that says “hey, if you’re using Python 3.12+, don’t upgrade setuptools”.
The text was updated successfully, but these errors were encountered:
Let’s say that I create and activate a fresh virtual environment using Python 3.13. When I run the command python -m pip install --upgrade pip setuptools, it will install the setuptools package because the setuptools package wasn’t already installed. Is installing the setuptools package manually the right thing to do in this scenario? Will I not have access to packaging if I don’t manually install setuptools? I had assumed that pip would get all of the build dependencies for me when I ran pip install --editable ".[dev]", but I’m not an expert in Python packaging.
docs/Hacking.md
says:As of Python 3.12, Python no longer comes with the
setuptools
package by default. I tried following the instructions indocs/Hacking.md
in a fresh Python 3.13 virtual environment, but I skipped installing/upgradingsetuptools
(I only upgradedpip
). Everything worked fine.At some point,
docs/Hacking.md
so that it doesn’t tell users to upgradesetuptools
. We could do it after Python 3.10 has reached end of life, or we could do it sooner with a note that says “hey, if you’re using Python 3.12+, don’t upgradesetuptools
”.The text was updated successfully, but these errors were encountered: