iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update from Jesse addressing API renaming to comply with PEP 8.

This commit is contained in:
Guido van Rossum 2008-06-03 21:11:26 +00:00
parent bc5e283eac
commit 06efb622d8
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pep-0371.txt
View File

@ -219,7 +219,7 @@ Performance Comparison
does hinder non-I/O applications. Obviously, these tests could be
improved to use a queue for coordination of results and chunks of
work but that is not required to show the performance of the
package and core Processing module.
package and core processing.process module.
The next test is an I/O bound test. This is normally where we see
a steep improvement in the threading module approach versus a
@ -318,15 +318,15 @@ Maintenance
API Naming
The API of the pyprocessing package is designed to closely mimic
that of the threading and Queue modules. It has been proposed that
instead of adding the package as-is, we rename it to be PEP 8
compliant instead.
While the aim of the package's API is designed to closely mimic that of
the threading and Queue modules, those modules are not PEP 8 compliant.
It has been decided that instead of adding the package as-is and
therefore perpetuating the non-PEP 8 compliant naming, we will rename
all APIs, classes, etc to be fully PEP 8 compliant.
Since the aim of the package is to be a drop-in for the threading
module, the authors feel that the current API should be used.
When the threading and Queue modules are updated to fully reflect
PEP 8, the pyprocessing/multiprocessing naming can be revised.
This change does affect the ease-of-drop in replacement for those using
the threading module, but that is an acceptable side-effect in the view
of the authors.
Timing/Schedule