Message 60083 - 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	cwalther
Recipients	Rhamphoryncus, amaury.forgeotdarc, brett.cannon, cwalther, gregory.p.smith
Date	2008-01-18.08:54:59
SpamBayes Score	0.00143429
Marked as misclassified	No
Message-id	<1200646502.59.0.595886054866.issue1596321@psf.upfronthosting.co.za>
In-reply-to

Content
> Is the bug avoided if you import threading first and use it instead of thread? Yes. The bug happens when the (first) import of threading and the call to Py_Finalize() happen in different threads. To reproduce the problem in pure Python, I therefore have to use thread instead of threading to create the secondary thread. (In the C++ application, it's created on the C++ side.) Has anyone checked if the solution I propose in the first post makes sense?

> Is the bug avoided if you import threading first and use it instead of thread?

Yes. The bug happens when the (first) import of threading and the call to Py_Finalize() 
happen in different threads. To reproduce the problem in pure Python, I therefore have to 
use thread instead of threading to create the secondary thread. (In the C++ application, 
it's created on the C++ side.)

Has anyone checked if the solution I propose in the first post makes sense?

History
Date	User	Action	Args
2008-01-18 08:55:03	cwalther	set	spambayes_score: 0.00143429 -> 0.00143429 recipients: + cwalther, brett.cannon, gregory.p.smith, amaury.forgeotdarc, Rhamphoryncus
2008-01-18 08:55:02	cwalther	set	spambayes_score: 0.00143429 -> 0.00143429 messageid: <1200646502.59.0.595886054866.issue1596321@psf.upfronthosting.co.za>
2008-01-18 08:55:01	cwalther	link	issue1596321 messages
2008-01-18 08:54:59	cwalther	create