➜

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.

作者 gregory.p.smith
收信人 Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, gvanrossum
日期 2008-01-17.21:32:18
SpamBayes Score 0.018540945
Marked as misclassified 否
Message-id <1200605539.87.0.325468843583.issue1856@psf.upfronthosting.co.za>
In-reply-to
内容
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).
历史
日期 用户 动作 参数
2008-01-17 21:32:20gregory.p.smith修改spambayes_score: 0.0185409 -> 0.018540945
recipients: + gregory.p.smith, gvanrossum, amaury.forgeotdarc, Rhamphoryncus
2008-01-17 21:32:19gregory.p.smith修改spambayes_score: 0.0185409 -> 0.0185409
messageid: <1200605539.87.0.325468843583.issue1856@psf.upfronthosting.co.za>
2008-01-17 21:32:19gregory.p.smith链接issue1856 messages
2008-01-17 21:32:18gregory.p.smith创建