[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Changes by Antoine Pitrou : -- components: +Documentation -Library (Lib) resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Hynek Schlawack added the comment: The proposed patch has been committed as c4dcbe51c2e3 – any reasons why this issues is still open? -- nosy: +hynek ___ Python tracker ___

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Jesse Noller added the comment: Fine w/ committing this Ask. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Ask Solem added the comment: I created a small doc patch for this (attached). -- keywords: +needs review, patch nosy: +asksol versions: +Python 3.1 -Python 2.6 Added file: http://bugs.python.org/file18967/multiprocessing-issue7707.patch ___ Python tr

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Brett Cannon added the comment: Without looking at the multiprocessing code I am willing to guess that some code in that run() function is launching some code that runs in a thread that is performing an import, deadlocking on the import lock. Jesse, is that what could be happening? If so we s

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

Changes by R. David Murray : -- nosy: +brett.cannon, jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue7707] multiprocess.Queue operations during import can lead to deadlocks

New submission from Alon Zakai : Creating a multiprocessing.Queue and operating on it while being imported can lead to a deadlock. The attached file will work if run directly (python test.py) but will hang if imported from the interpreter (import test). Additional comments are in the file. -