[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue

Changes by Davin Potts : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list

[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue

Changes by Berker Peksag : -- nosy: +berker.peksag stage: -> needs patch type: -> enhancement versions: +Python 3.6 -Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker

[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue

Thomas Fenzl added the comment: Considering public API elements, there are more inconsistencies. E.g. Pool: 'imap' 'apply' 'join' 'map_async' 'Process' 'terminate' 'close' 'starmap_async' 'starmap' 'apply_async' 'map' 'imap_unordered' : Pool misses some public elements. What level of

[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue

Ray.Allen ysj@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

[issue8690] multiprocessing.dummy.Queue does not expose same interface as multiprocessing.Queue

New submission from Jason Baker amnorv...@gmail.com: The multiprocessing.dummy.Queue class is merely an import of Queue.Queue. There are a few methods that this does not provide however: close, join_thread, and cancel_join_thread. I don't know what the best way to handle this is, but it