On Wed, 14 Nov 2018 at 14:28, Victor Stinner <vstin...@redhat.com> wrote: > > assuming the experiment is successful, forced (as opposed to opt-in) > > migration to the new API would be handled in a gradual, > > No, the current C API will remain available. No one is forced to do > anything. That's not part of my plan.
Oh, cool. So current code will continue working indefinitely? What's the incentive for projects to switch to the new API in that case? Won't we just end up having to carry two APIs indefinitely? Sorry if this is all obvious, or was explained previously - as I said I've not been following precisely because I assumed it was all being handled on an "if you don't care you can ignore it and nothing will change" basis, but Raymond's comments plus your suggestion that you needed to test existing C extensions, made me wonder. If it is the case that there's no need for any 3rd party code to change in order to continue working with 3.8+, then I apologise for the interruption. Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
