On 4 Jun 2020, at 16:34, Victor Stinner
wrote: Le jeu. 4 juin 2020 à 00:14, Nathaniel Smith
a écrit : On Wed, Jun 3, 2020 at 2:10 PM Victor Stinner
wrote: For the short term, my plan is to make structure opaque in the limited C API, before breaking more stuff in the public C API :-)
But you're also breaking the public C API: https://github.com/MagicStack/immutables/issues/46 https://github.com/pycurl/pycurl/pull/636
I'm not saying you're wrong to do so, I'm just confused about whether your plan is to break stuff or not and on which timescale.
Yes, my plan includes backward incompatible changes on purpose: https://github.com/vstinner/misc/blob/master/cpython/pep-opaque-c-api.rst#ap...
The practical issue is to estimate how many C extension modules are broken by a specific C API change. I plan to help out to port C extensions to the updated C API. If the number of broken extensions is fine and updating them is easy/short: fine! If the number is too high, we have until "3.10.0 final: Monday, 2021-10-04" to revert incompatible changes which caused most troubles.
snip My experience with keeping PyCXX up to date with these changes is that its not hard to be compatible. I support python 3.4 to 3.9 for limited and unlimited API. (I also support python 2.7 with the same unlimited API) Barry
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-leave@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/23LYPNHS... Code of Conduct: http://python.org/psf/codeofconduct/