Author ncoghlan
Recipients docs@python, eric.snow, ncoghlan, ned.deily, vstinner, xiang.zhang
Date 2018-06-22.11:26:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529666815.13.0.56676864532.issue33932@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2018-06-22 11:26:55ncoghlansetrecipients: + ncoghlan, vstinner, ned.deily, docs@python, eric.snow, xiang.zhang
2018-06-22 11:26:55ncoghlansetmessageid: <1529666815.13.0.56676864532.issue33932@psf.upfronthosting.co.za>
2018-06-22 11:26:55ncoghlanlinkissue33932 messages
2018-06-22 11:26:55ncoghlancreate