Since distutils does not change, why remove it? It is a lot of work for people with little gain.
If we don't remove it, we should at least freeze the bug component so that people cannot report bugs in distutils. Triaging these bugs alone is a decent amount of work. We should probably also set up a Bedevere to auto-reject PRs that touch distutils files (since telling people that distutils is frozen and no longer maintained is effort as well), and disable distutils in the CI so that it does not generate work for people maintaining the buildbots.
How often do you actually build extensions without building or installing external packages? You don't use `pip install` or PEP 517 builds? Just legacy build and installs? Do you not build or release wheels (which requires the `wheel` package)? Are you planning to upload artifacts to PyPI — if so, won't you need an external package (or at least a maintained package that can keep up with the APIs? Before we deprecated and removed it in setuptools, setup.py upload was causing problems with the metadata it uploaded — we may need to ban distutils-created packages from PyPI in order to keep PyPI going).I'd really like to build C extensions without downloading an external package.
Considering that we aren't adding anything to distutils today, the chances of this happening in setuptools are pretty much strictly better than in distutils.Features like C++ support have not been worked on for more than a decade. Are the setuptools maintainers planning to address these issues now?
* Modules/_decimal/tests/formathelper.pyelif find_executable('locale'): locale_list = subprocess.Popen(["locale", "-a"], stdout=subprocess.PIPE).communicate()[0] One of the many things that just work out of the box. -10 on removing distutils from the stdlib. Freezing it is fine. Stefan Krah _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/6LQN5OAJQSEJS6YHRZNK4QORJXCHLPHA/ Code of Conduct: http://python.org/psf/codeofconduct/