Created on 2010-01-15 16:35 by kripken, last changed 2010-11-05 14:53 by jnoller.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| test.py | kripken, 2010-01-15 16:35 | test cases | ||
| multiprocessing-issue7707.patch | asksol, 2010-09-22 19:19 | |||
| Messages (4) | |||
|---|---|---|---|
| msg97820 - (view) | Author: Alon Zakai (kripken) | Date: 2010-01-15 16:35 | |
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. |
|||
| msg97846 - (view) | Author: Brett Cannon (brett.cannon) *  |
Date: 2010-01-15 21:10 | |
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 should probably add a note to the multiprocessing docs to not do this sort of stuff, ala http://docs.python.org/library/threading.html#importing-in-threaded-code . |
|||
| msg117151 - (view) | Author: Ask Solem (asksol) |
Date: 2010-09-22 19:19 | |
I created a small doc patch for this (attached). |
|||
| msg120504 - (view) | Author: Jesse Noller (jnoller) * |
Date: 2010-11-05 14:53 | |
Fine w/ committing this Ask. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-05 14:53:20 | jnoller | set | messages: + msg120504 |
| 2010-09-22 19:19:58 | asksol | set | files:
+ multiprocessing-issue7707.patch versions: + Python 3.1, - Python 2.6 nosy: + asksol messages: + msg117151 keywords: + needs review, patch |
| 2010-01-15 21:10:43 | brett.cannon | set | assignee: jnoller messages: + msg97846 |
| 2010-01-15 17:26:15 | r.david.murray | set | nosy:
+ brett.cannon, jnoller |
| 2010-01-15 16:35:13 | kripken | create | |