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 jcmuel
Recipients docs@python, jcmuel
Date 2018-09-13.18:25:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536863152.32.0.956365154283.issue34665@psf.upfronthosting.co.za>
In-reply-to
Content
Since about a decade, it's a know problem that NumPy and Pandas initialization function crashes on reinitialization after a call to Py_Finalize() + Py_Initialize().

[https://github.com/numpy/numpy/issues/8097]
[https://github.com/numpy/numpy/issues/11925]

It seems to be unlikely that this problem gets fixed soon. Due to the popularity of the modules, it would be good to add this information to the documentation of Py_FinalizeEx(), such that developers, who are planning to embed Python get this information already at the moment when they read the documentation.

I would suggest to change the following sentence:

    Some extensions may not work properly if their
    initialization routine is called more than once;

to

    Some extensions, like NumPy and Pandas, may not work properly if their
    initialization routine is called more than once;
History
Date User Action Args
2018-09-13 18:25:52jcmuelsetrecipients: + jcmuel, docs@python
2018-09-13 18:25:52jcmuelsetmessageid: <1536863152.32.0.956365154283.issue34665@psf.upfronthosting.co.za>
2018-09-13 18:25:52jcmuellinkissue34665 messages
2018-09-13 18:25:52jcmuelcreate