This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients docs@python, eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2017-11-24.21:33:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511559183.6.0.213398074469.issue32124@psf.upfronthosting.co.za>
In-reply-to
Content
> Then document this explicitly like for other functions that *should* be called before Py_Initialize() if called at all.

I agree that it would be even better to document if a function must not be called after Py_Initialize().

*But* I'm not sure of what I wrote, I have to check the code, and maybe even test manually to "see what happens" (ensure that it works) :-)

So I decided to push my first PR, and will work on a second PR later.
History
Date User Action Args
2017-11-24 21:33:03vstinnersetrecipients: + vstinner, ncoghlan, docs@python, eric.snow, serhiy.storchaka
2017-11-24 21:33:03vstinnersetmessageid: <1511559183.6.0.213398074469.issue32124@psf.upfronthosting.co.za>
2017-11-24 21:33:03vstinnerlinkissue32124 messages
2017-11-24 21:33:03vstinnercreate