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 eric.snow
Recipients eric.snow, pconnell
Date 2019-12-20.23:54:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1576886041.93.0.942317170669.issue36476@roundup.psfhosted.org>
In-reply-to
Content
To put it another way:

(from issue33608#msg358748)

> The docs [1] aren't super clear about it, but there are some fundamental
> assumptions we make about runtime finalization:
>
> * no use of the C-API while Py_FinalizeEx() is executing (except for a
> few helpers like Py_Initialized)
> * only a small portion of the C-API is available afterward (at least
> until Py_Initialize() is run)
>
> I guess the real question is what to do about this?
> 
>[1] https://docs.python.org/3/c-api/init.html#c.Py_FinalizeEx

Adding to that list:

* no other Python threads are running once we start finalizing the runtime (not far into Py_FinalizeEx())
History
Date User Action Args
2019-12-20 23:54:01eric.snowsetrecipients: + eric.snow, pconnell
2019-12-20 23:54:01eric.snowsetmessageid: <1576886041.93.0.942317170669.issue36476@roundup.psfhosted.org>
2019-12-20 23:54:01eric.snowlinkissue36476 messages
2019-12-20 23:54:01eric.snowcreate