[issue26905] from multiprocessing.pool import Pool bug on linux

2016-05-02 Thread SilentGhost
Changes by SilentGhost : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue26905] from multiprocessing.pool import Pool bug on linux

2016-05-02 Thread Josh Rosenberg
Josh Rosenberg added the comment: The Queue module (queue on Py3) is for communication between threads, not processes; what you've written wouldn't behave correctly on any version of Python. You want to use multiprocessing's Queue class, not Queue.Queue, and to avoid possible deadlocks, you wa

[issue26905] from multiprocessing.pool import Pool bug on linux

2016-05-02 Thread SilentGhost
Changes by SilentGhost : -- nosy: +jnoller, sbt -larry type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue26905] from multiprocessing.pool import Pool bug on linux

2016-05-02 Thread Larry Hastings
Larry Hastings added the comment: This has nothing to do with Argument Clinic, which is an internal tool used in the Python 3.x series. -- components: -Argument Clinic nosy: -859911096 ___ Python tracker ___

[issue26905] from multiprocessing.pool import Pool bug on linux

2016-05-02 Thread yangming
New submission from yangming: When my code run on windows,it's right,but on linux,id(q) print same RAM address. -- components: Argument Clinic files: pool.py messages: 264637 nosy: 859911096, larry priority: normal severity: normal status: open title: from multiprocessing.pool import Po