PEP 755: Status quo of the CPython 3.12 build system #3
Conversation
|
cc. @zware |
- Don't treat the docs build as a separate build system; it is not - Don't call GNU Autoconf a 'fragile project' - Remove TODO comments
|
I'm wondering if this is too small for a PEP. It's hard to say. With the larger project in mind1, it makes sense to carefully progress PEP by PEP. Replacing the whole build system is a topic bound to generate heated discussions, so I think it makes sense to be overly bureaucratic, and manifest the summarisation of our polls in a (small) PEP. Footnotes
|
|
I agree with that assessment. I'm not sure that this is really a PEP per se, but in the same way that I don't think PEPs 482 and 483 are really PEPs. But it's the mechanism we've got, so a PEP it is :) |
erlend-aasland
changed the title
Exactly :) So, I guess the only remaining issue now is to polish the title and perhaps also adjust wording in the abstract. |
|
Should we post a heads-up on Discourse, or just submit the PEP? |
|
I think we might want to have the next PEP ready to go before posting this one to help this better fit as a PEP. I'm still trying to find time to actually read all the way through this one though :( |
I agree, and I've thought about the same. |
* Expand/correct Windows section * Shorten URLs * Minor grammar fixups * Add a couple of rewording possibilities as comments
📚 Documentation preview 📚: https://pep-previews--3.org.readthedocs.build/