There is a work-in-progress PR to document this organization: https://github.com/python/cpython/pull/24884
Victor
On Wed, Mar 17, 2021 at 8:03 PM Antoine Pitrou <antoine@python.org> wrote:
Le 17/03/2021 à 19:00, Eric Snow a écrit :
Finally, is the separation of headers by access "rings" worth it? On the one hand it makes the divisions explicit and obvious and helps avoid API leaking out accidentally. We'd had success in that regard with Include/internal and Include/cpython. On the other hand, the divisions mean related API is often spread out across multiple files (albeit with matching names), where otherwise those would all be in one file.
For the record, as a currently occasional contributor, I find the current organization of headers very cumbersome to navigate. The former flat organization was much better IMHO.
Regards
Antoine.
capi-sig mailing list -- capi-sig@python.org To unsubscribe send an email to capi-sig-leave@python.org https://mail.python.org/mailman3/lists/capi-sig.python.org/ Member address: vstinner@python.org
-- Night gathers, and now my watch begins. It shall not end until my death.