New submission from Noah Yetter: Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information. The docs claim that "multiprocessing.dummy replicates the API of multiprocessing but is no more than a wrapper around the threading module." however dummy's Pool method does not replicate the API of multiprocessing's Pool method: >>> import inspect >>> import multiprocessing >>> inspect.getargspec(multiprocessing.Pool) ArgSpec(args=['processes', 'initializer', 'initargs', 'maxtasksperchild'], varargs=None, keywords=None, defaults=(None, None, (), None)) >>> import multiprocessing.dummy >>> inspect.getargspec(multiprocessing.dummy.Pool) ArgSpec(args=['processes', 'initializer', 'initargs'], varargs=None, keywords=None, defaults=(None, None, ())) Thus when attempting to downshift from multiprocessing to threading like so... import multiprocessing.dummy as multiprocessing ...code that supplies the maxtasksperchild argument to Pool() will not run. ---------- components: Library (Lib) messages: 181365 nosy: Noah.Yetter priority: normal severity: normal status: open title: multiprocessing.dummy.Pool does not accept maxtasksperchild argument type: behavior versions: Python 2.7, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17127> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
