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 barry, benjamin.peterson, jnoller, mishok13, ncoghlan
Date 2008-08-19.16:09:17
SpamBayes Score 0.0009035321
Marked as misclassified No
Message-id <1219162158.93.0.60870209826.issue3352@psf.upfronthosting.co.za>
In-reply-to
Content
Just saw a couple of docs checkins go by suggesting that the camelCase
names will be unavailable in 3.x. Remember that the intent *isn't* to
remove the old names from threading.py - we're just adding the PEP 8
names so that multiprocessing can have a PEP 8 compliant API while still
being close to a drop-in replacement for the 2.6 version of the
threading module.

This means that all of the DeprecationWarnings and so forth can be left
out completely.

Regarding your patch Jesse:
- if I remember rightly, get_exitcode() can block waiting for the other
process to finish, which makes turning it into a property a fairly
questionable idea (p.get_exitcode() blocking is a lot less surprising
than "p.exitcode" doing so)
- the get/set documentation for the new properties can probably be
consolidated, but that isn't a major problem as far as this week's beta
is concerned.
History
Date User Action Args
2008-08-19 16:09:19ncoghlansetrecipients: + ncoghlan, barry, benjamin.peterson, jnoller, mishok13
2008-08-19 16:09:18ncoghlansetmessageid: <1219162158.93.0.60870209826.issue3352@psf.upfronthosting.co.za>
2008-08-19 16:09:18ncoghlanlinkissue3352 messages
2008-08-19 16:09:18ncoghlancreate