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 TheUltimatePineapple, chris.jerdonek, christian.heimes, ned.deily, pmpp, remi.lapeyre
Date 2020-06-07.03:41:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591501281.12.0.803584749296.issue40743@roundup.psfhosted.org>
In-reply-to
Content
Thanks for your suggestion but changing build systems is a *huge* undertaking for cPython thanks to the many different platforms that we have added support to over the years and the many, many customizations that have been made.  cmake would certainly be one option; starting from scratch with modern autotools another. And there are many such others. But this is way beyond the scope of a standard feature enhancement. In fact, there have been some discussions around the PSF funding one or more persons to reimplement our Unix-y build system (note there is a separate build system for Windows platforms). As Christian suggests, one concrete step towards getting a new build system would be to write a detailed PEP and then discussing in the ideas and/or core-workflow groups; another would be to help secure funding.  But without first steps like that, there won't be anything served by further discussions here. So I'm closing this issue. It could be re-opened in the future once there is consensus on an approach and implementation resources are identified.
History
Date User Action Args
2020-06-07 03:41:21ned.deilysetrecipients: + ned.deily, christian.heimes, pmpp, chris.jerdonek, remi.lapeyre, TheUltimatePineapple
2020-06-07 03:41:21ned.deilysetmessageid: <1591501281.12.0.803584749296.issue40743@roundup.psfhosted.org>
2020-06-07 03:41:21ned.deilylinkissue40743 messages
2020-06-07 03:41:20ned.deilycreate