Gabriel Genellina gagsl-py2 at yahoo.com.ar
Sat Jan 17 05:32:35 EST 2009

• Previous message (by thread): Python 2.6's multiprocessing lock not working on second use?
• Next message (by thread): Python 2.6's multiprocessing lock not working on second use?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

En Fri, 16 Jan 2009 14:41:21 -0200, escribiste en el grupo
gmane.comp.python.general

> I ran a few tests on the new Python 2.6 multiprocessing module before
> migrating a threading code, and found out the locking code is not
> working well. In this case, a pool of 5 processes is running, each
> trying to get the lock and releasing it after waiting 0.2 seconds
> (action is repeated twice). It looks like the multiprocessing lock
> allows multiple locking after the second pass. Running the exact same
> code with threads works correctly.

I've tested your code on Windows and I think the problem is on the Queue
class. If you replace the Queue with some print statements or write to a
log file, the sequence lock/release is OK.
You should file a bug report on http://bugs.python.org/

-- 
Gabriel Genellina

---

• Previous message (by thread): Python 2.6's multiprocessing lock not working on second use?
• Next message (by thread): Python 2.6's multiprocessing lock not working on second use?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list