Message121507
+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? |
|
Date |
User |
Action |
Args |
2010-11-19 10:08:28 | ysj.ray | set | recipients:
+ ysj.ray, Jason.Baker |
2010-11-19 10:08:28 | ysj.ray | set | messageid: <1290161308.79.0.538719401131.issue8690@psf.upfronthosting.co.za> |
2010-11-19 10:08:27 | ysj.ray | link | issue8690 messages |
2010-11-19 10:08:27 | ysj.ray | create | |
|