[Python-Dev] bug 754449 and threads raising exceptions at interpreter teardown

Jeremy Hylton jeremy at alum.mit.edu
Tue Feb 10 14:25:52 EST 2004

On Tue, 2004-02-10 at 13:54, "Martin v. Löwis" wrote:
> Brett wrote:
> > So you are classifying this as a bug then.  That was part of my question 
> > since it only happens if you don't handle your threads properly (or at 
> > least I think properly; I would assume it is common practice to close 
> > down your threads).
> Certainly: in a properly working program, one would terminate all
> threads first before trying to exit the program. Failure to do so
> should cause an exception (or otherwise have an "obvious" meaning).
> However, that exception should not be a "double-fault"; instead,
> it should give a clear indication what the problem is.

What about daemon threads?  They are running by intention when the
program exits, otherwise they wouldn't be daemon threads.


More information about the Python-Dev mailing list