This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mdk
Recipients Marcus.Smith, dstufft, eric.araujo, eric.snow, jaraco, lkollar, lukasz.langa, mdk, ncoghlan, pablogsal, paul.moore, pradyunsg, steve.dower
Date 2021-01-12.13:05:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1610456723.09.0.258760302895.issue41490@roundup.psfhosted.org>
In-reply-to
Content
Question: Why do we keep setuptools?

According to PEP453:

> Once pip is able to run pip install --upgrade pip without needing setuptools installed first, then the private copy of setuptools will be removed from ensurepip in subsequent CPython releases.

Which looks like to be the fact now:

    $ python3.9 -m venv .venv
    $ source .venv/bin/activate
    $ pip uninstall setuptools
    [...]
    Successfully uninstalled setuptools-49.2.1
    $ pip install --upgrade pip
    [...]
    Successfully installed pip-20.3.3
History
Date User Action Args
2021-01-12 13:05:23mdksetrecipients: + mdk, paul.moore, jaraco, ncoghlan, eric.araujo, lukasz.langa, eric.snow, steve.dower, dstufft, pradyunsg, Marcus.Smith, lkollar, pablogsal
2021-01-12 13:05:23mdksetmessageid: <1610456723.09.0.258760302895.issue41490@roundup.psfhosted.org>
2021-01-12 13:05:23mdklinkissue41490 messages
2021-01-12 13:05:23mdkcreate