On Fri, Feb 11, 2022 at 3:14 PM Petr Viktorin <encu...@gmail.com> wrote: > Sounds reasonable, but... > > The implication of endorsing code like this is that *we cannot change > private API even in patch releases*, which I don't think is documented > anywhere, and might be a bit controversial. > (I'm still planning to document this along with other similar issues, so > if anyone wants to help here, please coordinate with me: > https://discuss.python.org/t/documenting-python-versioning-and-stability-expectations/11090/4).
Maybe... we should not do that :-D The PyGC_Head ABI change was the most controversial, but it was already part of the private API and the following bug was closed as "not a bug": https://bugs.python.org/issue39599 This structure now belings to the *internal* C API. > Since you're now inviting the wider community as co-maintainers, could > you document this? Well, anyone is welcomed to contribute! 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/WZTVXVBSYS5J3PITADSIYI32KZEJS2MR/ Code of Conduct: http://python.org/psf/codeofconduct/
