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 ncoghlan
Recipients ncoghlan
Date 2008-07-14.09:57:52
SpamBayes Score 0.0027329074
Marked as misclassified No
Message-id <1216029476.59.0.254562018699.issue3352@psf.upfronthosting.co.za>
In-reply-to
Content
The "PEP 8 compliant" API for multiprocessing and threading needs to be
cleaned up before release as per the thread on python-dev. The release
manager gave approval for this change during that discussion [1].

Changes needed:
- remove Py3k warnings from the threading module (old API is going to be
kept around even in Py3k)
- change get_name/set_name into a "name" property
- change is_daemon/set_daemon into a "daemon" property

(Note that changing "is_alive" to be a property is not on that list -
that can be a fairly expensive thing to check for the multiprocessing
library. I also left out active_count(), as I think the underscore adds
clarity in that case)

[1] http://mail.python.org/pipermail/python-dev/2008-June/080285.html
History
Date User Action Args
2008-07-14 09:58:04ncoghlansetspambayes_score: 0.00273291 -> 0.0027329074
recipients: + ncoghlan
2008-07-14 09:57:56ncoghlansetspambayes_score: 0.00273291 -> 0.00273291
messageid: <1216029476.59.0.254562018699.issue3352@psf.upfronthosting.co.za>
2008-07-14 09:57:55ncoghlanlinkissue3352 messages
2008-07-14 09:57:53ncoghlancreate