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 jnoller
Recipients georg.brandl, ggenellina, jnoller, steve21
Date 2009-01-24.00:54:05
SpamBayes Score 1.008031e-05
Marked as misclassified No
Message-id <4222a8490901231654k4c8d2816y75cb5deec8fe724a@mail.gmail.com>
In-reply-to <1232756943.27.0.858281119222.issue5031@psf.upfronthosting.co.za>
Content
> 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 ..."""
History
Date User Action Args
2009-01-24 00:54:06jnollersetrecipients: + jnoller, georg.brandl, ggenellina, steve21
2009-01-24 00:54:05jnollerlinkissue5031 messages
2009-01-24 00:54:05jnollercreate