Message305280
| Author |
ncoghlan |
| Recipients |
Dormouse759, eric.snow, grahamd, ncoghlan, petr.viktorin |
| Date |
2017-10-31.09:46:06 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1509443166.44.0.213398074469.issue31901@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
I guess we allow an unhandled SystemExit in a child thread to propagate to (and hence terminate) the main thread, so allowing a Py_Finalize call in a subinterpreter to terminate the main interpreter would be comparable to that.
My main rationale for *requiring* that the main interpreter be active (or be made active) when shutting down is to reduce the number of scenarios we need to test (right now we only test Py_Initialize/Py_Finalize cycles with a single interpreter, and officially allowing finalization from arbitrary interpreters expands that test matrix a fair bit). |
|