Re: [Python-Dev] Re: [Python-checkins] python/dist/src/Lib/test test_signal.py,1.9,1.10
Guido van Rossum <guido@python.org> writes:
Does anyone want to explain BSD threads and their interaction with signals to me?
Yes. Threads and signals don't mix. Period. (Only half a smiley. :-)
Well, I'm not mixing threads and signals, really. I've now learnt that when a signal is directed at a process on BSD it is delivered to "a" signal from the set of signals that hasn't blocked it. What I need to know, and can't quite work out, is how many threads are present when you just execute $ ./python and are sitting at the interpreter prompt? Is it just the one (the main thread)? That's what I thought, but I'm unable to explain the behaviour I'm seeing if that is indeed the case. Cheers, M. -- [3] Modem speeds being what they are, large .avi files were generally downloaded to the shell server instead[4]. [4] Where they were usually found by the technical staff, and burned to CD. -- Carlfish, asr
Well, I'm not mixing threads and signals, really. I've now learnt that when a signal is directed at a process on BSD it is delivered to "a" signal from the set of signals that hasn't blocked it. ^^^^^^ ^^^^^^^
You mean theads, right?
What I need to know, and can't quite work out, is how many threads are present when you just execute
$ ./python
and are sitting at the interpreter prompt? Is it just the one (the main thread)? That's what I thought, but I'm unable to explain the behaviour I'm seeing if that is indeed the case.
Python doesn't create any threads. On Linux, I know that when you start your first thread, the thread library creates an extra thread for some internal reasons. Who knows what BSD does though. --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Guido van Rossum -
Michael Hudson