Vinay Sajip wrote: > > Right, I'm > > pretty sure that right now Python doesn't have any way to > > share symbols between .c files without also exposing them in the C > > API. > > On other C projects I've worked on, the public API is expressed in one set > of header files, and internal APIs that need to be exposed across modules are > described in > a different set of internal header files, and developers who incorrectly use > internal APIs > by including the internal headers could see breakage when the internals > change ... excuse > my naïveté, as I haven't done much at Python's C level - does this > discipline/approach not > apply to CPython?
As of Python 3.8 we do this sort of separation: https://docs.python.org/3.8/whatsnew/3.8.html#build-and-c-api-changes. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/GS2GJDU6J4RXWPHDB5UJJTHLVULOGVLX/
