[issue3589] Misleading names for multiprocessing "convenience" functions
report at bugs.python.org
Tue Sep 2 00:11:26 CEST 2008
Antoine Pitrou <pitrou at free.fr> added the comment:
Le lundi 01 septembre 2008 à 21:22 +0000, Nick Coghlan a écrit :
> As Fredrik noted in the python-dev thread, the threading versions of
> these are already explicitly documented as being factory functions
> rather than classes (and as a reference to _thread.allocate_lock,
> threading.Lock has good reason to be a factory function rather than a
> class), so it may be appropriate to do the same thing for multiprocessing.
"Foolish consistency, etc.". :-)
I think we should fix this before the releases rather than live with a
stupid indirection that doesn't seem to serve any useful purposes.
Unless the fix is too complicated of course.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list