Antoine Pitrou <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> <http://bugs.python.org/issue3589> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
