➜

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 Rhamphoryncus
Recipients Rhamphoryncus, brett.cannon, ggenellina, gpk, jamescooper, thomasda, yangzhang
Date 2008-02-05.21:24:47
SpamBayes Score 0.045995113
Marked as misclassified No
Message-id <1202246749.31.0.474306743872.issue1722344@psf.upfronthosting.co.za>
In-reply-to
Content 
Py_Main calls WaitForThreadShutdown before calling Py_Finalize, which
should wait for all these threads to finish shutting down before it
starts wiping their globals.

However, if SystemExit is raised (such as via sys.exit()), Py_Exit is
called, and it directly calls Py_Finalize, bypassing the
WaitForThreadShutdown.

Can someone who's experienced this bug check if they're using
SystemExit/sys.exit?
History
Date User Action Args
2008-02-05 21:25:49Rhamphoryncussetspambayes_score: 0.0459951 -> 0.045995113
recipients: + Rhamphoryncus, brett.cannon, gpk, ggenellina, yangzhang, thomasda, jamescooper
2008-02-05 21:25:49Rhamphoryncussetspambayes_score: 0.0459951 -> 0.0459951
messageid: <1202246749.31.0.474306743872.issue1722344@psf.upfronthosting.co.za>
2008-02-05 21:24:48Rhamphoryncuslinkissue1722344 messages
2008-02-05 21:24:47Rhamphoryncuscreate