> 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/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4