[Python-Dev] PEP 371: Additional Discussion
Guido van Rossum
guido at python.org
Wed Jun 4 19:42:54 CEST 2008
Sounds good. (Maybe you want to contribute a patch to threading.py?
Your implementation notes are important. It could be quite independent
from PEP 371.)
On Wed, Jun 4, 2008 at 3:33 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> Jesse Noller wrote:
>> Per feedback from Guido, the python-dev list and others, I have sent
>> in an updated version of PEP 371 - the inclusion of the pyprocessing
>> module into the standard library.
>> URL: http://www.python.org/dev/peps/pep-0371/
>> New highlights:
>> * The module will be renamed to "multiprocessing"
>> * The API will become PEP 8 compliant
> My 2 cents on this: PEP 8 compliance in the multiprocessing API is a good
> idea, but threading should be updated at the same time to provide PEP 8
> compliant aliases for the existing names. Using the old Java-based names
> should provoke a Py3k warning in 2.6 (note: to avoid a runtime performance
> hit when not using -3, the actual function definitions should be made
> conditional, rather than checking whether or not to emit the warning every
> time the legacy API is invoked)
> The PyGILState_* bug in debug builds that RMO pointed out should also be
> mentioned in the PEP as something that needs to be fixed in order to
> implement the PEP.
>  http://bugs.python.org/issue1683
> Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
> Python-Dev mailing list
> Python-Dev at python.org
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev