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 ned.deily
Recipients dstufft, eric.araujo, jaraco, lukasz.langa, ncoghlan, ned.deily, pablogsal, paul.moore, steve.dower
Date 2020-07-13.07:28:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So what is the plan to continue to support building cpython itself which depends on Distutils? Currently the build bootstraps itself without the aid of an existing Python interpreter instance. There would also be major impacts across the whole cpython development process. For example, there are many open Distutils issues in the bug tracker. We need a plan on how those are to be handled (and that should take into account the expected transition from b.p.o to GitHub issues).  People will continue to submit issues agains Distutils there so triage team members and core developers need to know how to handle such issues.  What if an issue applies also or only to a previous release branch (i.e. where Distutils is still in the repo)?  What about Distutils documentation in the Python docset?  THose are just some off the top of my head.

I don't think any of these issues are necessarily blockers but they need to be planned for and reviewed.  I think a PEP is definitely in order for a change of this magnitude.
Date User Action Args
2020-07-13 07:28:23ned.deilysetrecipients: + ned.deily, paul.moore, jaraco, ncoghlan, eric.araujo, lukasz.langa, steve.dower, dstufft, pablogsal
2020-07-13 07:28:23ned.deilysetmessageid: <>
2020-07-13 07:28:23ned.deilylinkissue41282 messages
2020-07-13 07:28:23ned.deilycreate