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 cgoldberg
Recipients cgoldberg, georg.brandl
Date 2009-01-02.19:19:07
SpamBayes Score 6.87656e-06
Marked as misclassified No
Message-id <1230923948.55.0.326938770324.issue4808@psf.upfronthosting.co.za>
In-reply-to
Content
sorry for the confusion.  The doc might actually be correct, but it
seems ambiguous and confusing with respect to the name and daemon
properties.


if you look here:
http://docs.python.org/dev/py3k/library/threading.html

scroll down to where it says:

Thread.getName()
Thread.setName()
    Old API for name.

when you click on "name", it expands and shows you the 'name' property.
 However, it looks like it is denoting this as the "Old API".

at first glance it appears as though Thread.getName() and
Thread.setName() are the new way, and you can click on 'name' to see the
old API.  

I think the issue is actually the fact that Thread.name and
Thread.daemon are not expanded in the HTML doc until you click on their
names (unlike other properties/attributes in the doc which are already
expanded)

Let me know if I am not explaining well.
History
Date User Action Args
2009-01-02 19:19:08cgoldbergsetrecipients: + cgoldberg, georg.brandl
2009-01-02 19:19:08cgoldbergsetmessageid: <1230923948.55.0.326938770324.issue4808@psf.upfronthosting.co.za>
2009-01-02 19:19:08cgoldberglinkissue4808 messages
2009-01-02 19:19:07cgoldbergcreate