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 tim.peters
Recipients
Date 2002-07-15.03:48:13
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31435

Mark, we're running different code.  I'm talking about 
sleeper.py, which I attached to this bug report a few msgs 
back.  See the file attachment whose name is sleeper.py 
<wink>.  It doesn't use threading.py at all, just raw threads 
and raw locks from the thread module.  See that file and 
what I've been talking about will be clear.

About boosting the Sleep() argument, sure, that's 
reasonable.

I don't know anything about Linux quirks.  The design of the 
Windows gimmick here is such that any number of threads 
can wake up in the WaitForSingleObject().  If Linux happens 
to deliver SIGINT only to the main thread, then I suppose 
only the main thread will get KeyboardInterrupt on Linux.  
But I don't know what Linux does -- we'll have to suck a 
Linux geek in fo find out.
History
Date User Action Args
2007-08-23 14:04:13adminlinkissue581232 messages
2007-08-23 14:04:13admincreate