Python 2.6's multiprocessing lock not working on second use?

Jesse Noller jnoller at gmail.com
Mon Jan 19 20:40:46 CET 2009


On Mon, Jan 19, 2009 at 1:32 PM, Nick Craig-Wood <nick at craig-wood.com> wrote:
> Jesse Noller <jnoller at gmail.com> wrote:
>> > Opened issue #4999 [http://bugs.python.org/issue4999] on the matter,
>> > referencing this thread.
>>
>>  Thanks, I've assigned it to myself. Hopefully I can get a fix put
>>  together soonish, time permitting.
>
> Sounds like it might be hard or impossible to fix to me.  I'd love to
> be proved wrong though!
>
> If you were thinking of passing time.time() /
> clock_gettime(CLOCK_MONOTONIC) along in the Queue too, then you'll
> want to know that it can differ by significant amounts on different
> processors :-(
>
> Good luck!
>

Consider my parade rained on. And after looking at it this morning,
yes - this is going to be hard, and should be fixed for a FIFO queue
:\

-jesse



More information about the Python-list mailing list