[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue
Ray.Allen
report at bugs.python.org
Fri Nov 19 11:08:28 CET 2010
Ray.Allen <ysj.ray at gmail.com> added the comment:
+1 on make it identical to multiprossing.Queue. Since the documentation said:
multiprocessing.dummy replicates the API of multiprocessing but is no more than a wrapper around the threading module.
Does the word "replicates" implies that multiprossing.dummy.[AClass] should have the same interfaces as multiprossing.[AClass]? I think so. We should be able to use multiprossing.dummy.xxx wherever multiprossing.xxx can be used. We can just create a subclass of Queue.Queue and implemented these missing methods as dummy functions.
I wonder is there other inconsistence between multiprocessing.dummy and multiprocessing?
----------
nosy: +ysj.ray
versions: +Python 3.1, Python 3.2
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8690>
_______________________________________
More information about the Python-bugs-list
mailing list