Message181365
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. |
|
Date |
User |
Action |
Args |
2013-02-04 18:28:33 | Noah.Yetter | set | recipients:
+ Noah.Yetter |
2013-02-04 18:28:33 | Noah.Yetter | set | messageid: <1360002513.52.0.4376358205.issue17127@psf.upfronthosting.co.za> |
2013-02-04 18:28:33 | Noah.Yetter | link | issue17127 messages |
2013-02-04 18:28:33 | Noah.Yetter | create | |
|