Message 60059 - Python tracker

➜

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, amaury.forgeotdarc, gregory.p.smith, gvanrossum
Date	2008-01-17.21:00:48
SpamBayes Score	0.006826174
Marked as misclassified	No
Message-id	<1200603650.4.0.557134682777.issue1856@psf.upfronthosting.co.za>
In-reply-to

Content
I think non-main threads should kill themselves off if they grab the interpreter lock and the interpreter is tearing down. They're about to get killed off anyway, when the process exits. PyGILState_Ensure would still be broken. It touches various things that get torn down (autoInterpreterState, autoTLSkey, and the HEAD_LOCK macros) before it grabs the GIL. Reordering should be possible of course.

I think non-main threads should kill themselves off if they grab the
interpreter lock and the interpreter is tearing down.  They're about to
get killed off anyway, when the process exits.

PyGILState_Ensure would still be broken.  It touches various things that
get torn down (autoInterpreterState, autoTLSkey, and the HEAD_LOCK
macros) before it grabs the GIL.  Reordering should be possible of course.

History
Date	User	Action	Args
2008-01-17 21:00:50	Rhamphoryncus	set	spambayes_score: 0.00682617 -> 0.006826174 recipients: + Rhamphoryncus, gvanrossum, gregory.p.smith, amaury.forgeotdarc
2008-01-17 21:00:50	Rhamphoryncus	set	spambayes_score: 0.00682617 -> 0.00682617 messageid: <1200603650.4.0.557134682777.issue1856@psf.upfronthosting.co.za>
2008-01-17 21:00:48	Rhamphoryncus	link	issue1856 messages
2008-01-17 21:00:48	Rhamphoryncus	create