Message 182123 - 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	pitrou
Recipients	asvetlov, jcea, pitrou, sbt, serhiy.storchaka
Date	2013-02-14.22:32:57
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1360880977.3562.1.camel@localhost.localdomain>
In-reply-to	<1360856723.59.0.56869913329.issue15528@psf.upfronthosting.co.za>

Content
> But in Py_Finalize(), call_py_exitfuncs() is called before > _Py_Finalizing is set to a non-NULL value. > > > http://hg.python.org/cpython/file/0f827775f7b7/Python/pythonrun.c#l492 Ah, right. But is it any different from, e.g., registering an atexit handler from a daemon thread? In any case, I think it's just something we'll have to live with. Daemon threads are not a terrific idea in general.

> But in Py_Finalize(), call_py_exitfuncs() is called *before*
> _Py_Finalizing is set to a non-NULL value.
> 
> 
> http://hg.python.org/cpython/file/0f827775f7b7/Python/pythonrun.c#l492

Ah, right. But is it any different from, e.g., registering an atexit
handler from a daemon thread?
In any case, I think it's just something we'll have to live with. Daemon
threads are not a terrific idea in general.

History
Date	User	Action	Args
2013-02-14 22:32:57	pitrou	set	recipients: + pitrou, jcea, asvetlov, sbt, serhiy.storchaka
2013-02-14 22:32:57	pitrou	link	issue15528 messages
2013-02-14 22:32:57	pitrou	create