On Wed, Mar 30, 2022 at 2:26 AM Steve Dower <steve.do...@python.org> wrote: > Right now, the API is allowed/expected to change between 3.x releases > (which normally we don't allow without a deprecation period) but it > still has to remain compatible within a single 3.x release. Making it > fully internal *without adding a stability guarantee* means it could > change more frequently, which you wouldn't be able to handle as an > installable package. > > It's *unlikely* that it'll change that often, because there are still > other public interfaces that cannot. But, the plan behind this is to > make more stuff internal so that it can be modified more freely, so we > may see that rate of change increase.
Well, my plan is not break these internal C API just for fun. It's only to better "advertise" the separation between the "stable" public C API (backward compatibility warranty) and the "unstable" private/internal C API (can change any time, changes are not documented). Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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/OMGUI5N33BG3EU4OG3IUZXJQF6XU7X2B/ Code of Conduct: http://python.org/psf/codeofconduct/
