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 gregory.p.smith
Recipients Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, gvanrossum
Date 2008-01-17.21:32:18
SpamBayes Score 0.0185409
Marked as misclassified No
Message-id <>
agreed, during shutdown the other threads should be stopped.  anything
to do this complicates acquiring and releasing the GIL by adding another
check to see if we're shutting down.

brainstorm: I haven't looked at the existing BEGIN_ALLOW_THREADS and
END_ALLOW_THREADS implementations but would it be possible to modify
them on the fly from the thread doing the shutdown (main or not) while
it holds the GIL such that all future calls to BEGIN_ALLOW_THREADS do
not actually release the GIL and END_ALLOW_THREADS always blocks.  That
should bring other threads to a halt pretty quickly and prevent
destructors from releasing the GIL (file.close, etc).
Date User Action Args
2008-01-17 21:32:20gregory.p.smithsetspambayes_score: 0.0185409 -> 0.0185409
recipients: + gregory.p.smith, gvanrossum, amaury.forgeotdarc, Rhamphoryncus
2008-01-17 21:32:19gregory.p.smithsetspambayes_score: 0.0185409 -> 0.0185409
messageid: <>
2008-01-17 21:32:19gregory.p.smithlinkissue1856 messages
2008-01-17 21:32:18gregory.p.smithcreate