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 amaury.forgeotdarc
Recipients Rhamphoryncus, amaury.forgeotdarc, brett.cannon, cwalther, gregory.p.smith
Date 2008-01-17.20:04:10
SpamBayes Score 0.00045263345
Marked as misclassified No
Message-id <1200600253.88.0.576014803008.issue1596321@psf.upfronthosting.co.za>
In-reply-to
Content
If a python daemon thread is still running when the interpreter exits,
it is likely to fail in random ways.

Here is another example, which does not use imports.
I run the script many times, with latest version in trunk, on Windows
XP, debug build.

In the majority of runs, I get an error message:
"""
Exception in thread Thread-1 (most likely raised during interpreter
shutdown):
"""
Other tests seem to show that all modules are emptied by the cleanup
process, but the thread insists to get "time.sleep".

And more interestingly, about every 50 runs, the process segfaults...
I suspect that this is a problem similar to http://bugs.python.org/issue1856
History
Date User Action Args
2008-01-17 20:04:14amaury.forgeotdarcsetspambayes_score: 0.000452633 -> 0.00045263345
recipients: + amaury.forgeotdarc, brett.cannon, gregory.p.smith, Rhamphoryncus, cwalther
2008-01-17 20:04:13amaury.forgeotdarcsetspambayes_score: 0.000452633 -> 0.000452633
messageid: <1200600253.88.0.576014803008.issue1596321@psf.upfronthosting.co.za>
2008-01-17 20:04:11amaury.forgeotdarclinkissue1596321 messages
2008-01-17 20:04:10amaury.forgeotdarccreate