[docs] [issue33932] Calling Py_Initialize() twice now triggers a fatal error (Python 3.7)

Nick Coghlan report at bugs.python.org
Fri Jun 22 07:26:55 EDT 2018

Nick Coghlan <ncoghlan at gmail.com> added the comment:

While I agree the documentation issue means that this should be made to work again for Python 3.7.1, I'd like for Python 3.7 to at least deprecate calling Py_Initialize twice without an intervening Py_Finalize.

Otherwise the public multi-phase interpreter initialization API is going to have to cope with somebody starting the initialization process, and then calling a full Py_Initialize to finish it (instead of the new "complete initialization" API, whatever we end up calling that), and I'd prefer to keep the permitted state transitions more linear than that.


Python tracker <report at bugs.python.org>

More information about the docs mailing list