On 2018-09-12, Brett Cannon wrote:
I think we should just operate under the assumption that this project is going to be big enough that this is a Py4K project. There's no need to rush and I wouldn't want any release deadline to make people feel rushed.
I fear that scope creep is going to kill the initiative. So, I would like to see the API changes related to making alternative implementations work better (PyObject* as opaque pointer, no borrowed refs) become a separate project.
The new API would be the layer two API as dicussed above, without the ctx argument. We would take care to make sure that new API would be compatible with a later project to introduce the multi-interpreter safe API. Then we don't have to scare people about the prospect of changing 200k lines of CPython code to add the ctx argument.