On 2022-02-10 2:58 p.m., Victor Stinner wrote:
Would it make sense to move the pythoncapi_compat project under the GitHub Python or PSF organization to make it more "official" and a little bit more sustainable?
I think that makes sense. Extensions typically have this kind of compatibility code built into them, so they can support multiple Python versions. It makes more sense to centralize that code. It will be easier to keep up-to-date and will be better quality.
I think having the project more tightly associated with CPython is good too. When a change is made to the CPython extension API, it would be good to consider how pythoncapi_compat will need to be updated. E.g. how can extensions that want to support both old and new versions of the API work?
Regards, Neil _______________________________________________ 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/L62AAY6JZIYIRD7FYMC567XFM5PBAIZK/ Code of Conduct: http://python.org/psf/codeofconduct/
