[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-list
Subject:    RE: Apparently, I don't understand threading
From:       jwsacksteder () ramprecision ! com
Date:       2005-03-14 2:06:39
Message-ID: 71650A6F73F1D411BE8000805F65E3CB3B3E98 () SRV-03
[Download RAW message or body]

I realize that. I'm using a variant of the polite shutdown request technique
used in the python cookbook. The problem is that thread creation is
apparently blocking instead of continuing program execution.

-----Original Message-----
From: jepler@unpythonic.net [mailto:jepler@unpythonic.net] 
Sent: Sunday, March 13, 2005 9:03 PM
To: Jeff Sacksteder
Cc: python-list@python.org
Subject: Re: Apparently, I don't understand threading

The Python threading model doesn't allow one thread to forcibly terminate
another.  This has been discussed many times before, I think that the short
answer is a combination of (a) it's hard to specify what happens in the
terminated thread, without the possibility of leaving the program in an
unknown
state and (b) the threading modules are very lowest-common-denominator, not
requiring features that aren't already built into all the targeted
OS/threading
library combination.

Jeff
-- 
http://mail.python.org/mailman/listinfo/python-list
[prev in list] [next in list] [prev in thread] [next in thread]