- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message337392
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 | ncoghlan |
|---|---|
| Recipients | eric.snow, ncoghlan, petr.viktorin |
| Date | 2019-03-07.13:17:43 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1551964663.69.0.686712846789.issue36225@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
https://docs.python.org/3/c-api/init.html#c.Py_EndInterpreter states that "Py_FinalizeEx() will destroy all sub-interpreters that haven’t been explicitly destroyed at that point." As discussed in https://github.com/hexchat/hexchat/issues/2237, Python 3.7+ doesn't currently do that - it calls Py_FatalError instead. That change came from https://github.com/python/cpython/pull/1728, which was based on my initial PEP 432 refactoring work, and I didn't realise that implicitly cleaning up lingering subinterpreters was a documented behaviour. So I think we should just fix it to behave as documented, and add a new regression test to make sure it doesn't get broken again in the future. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-07 13:17:43 | ncoghlan | set | recipients: + ncoghlan, petr.viktorin, eric.snow |
| 2019-03-07 13:17:43 | ncoghlan | set | messageid: <1551964663.69.0.686712846789.issue36225@roundup.psfhosted.org> |
| 2019-03-07 13:17:43 | ncoghlan | link | issue36225 messages |
| 2019-03-07 13:17:43 | ncoghlan | create | |

