In the threading module the Thread.daemon documentation says:

"The thread’s daemon flag. This must be set before start() is called,
otherwise RuntimeError is raised.

    The initial value is inherited from the creating thread.

    The entire Python program exits when no alive non-daemon threads are
left."

I think the docs should state Thread.daemon's type (boolean, or integer,
or something else?) and its default value (when you have not set .daemon
in the creating thread.)

Attached is a patch to the docs which reflects the nature of the daemon 
property based on trunk

"This is a boolean value, and is False by default."

Not true; the next sentence in the description explains where the 
default value comes from.

I'd join both paragraphs to make it more clear:

"""A boolean value indicating whether this thread is a daemon thread 
(True) or not (False). This must be set before start() is called, 
otherwise RuntimeError is raised. Its initial value is inherited from 
the creating thread; the main thread is not a daemon thread.

The entire Python program exits ..."""

> Not true; the next sentence in the description explains where the
> default value comes from.

Hmm, unless your threads are spawned by daemonized threads; the value
always defaults to false. That's why I said it defaults to False. Hows
this:

"""A boolean value indicating whether this thread is a daemon thread
(True) or not (False). This must be set before start() is called,
otherwise RuntimeError is raised. Its initial value is inherited from
the creating thread; the main thread is not a daemon thread therefore
all threads created in the main thread default to daemon = False.

The entire Python program exits ..."""

Hows the new patch Gabriel?

Looks fine to me. Bah, perhaps purists would write `daemon` = 
``False`` , but I think the meaning is perfectly clear now.

Then the patch I wrote before "correcting it" was more purist ;) I 
preferred the `daemon` = ``False`` wording as well. Here's a corrected 
patch.

Committed in r69301.