r n added the comment:
Sorry, please ignore my previous comment, I can see that the issue is not in
the queue, but probably be somewhere in my setup.
I'll close this bug therefore. Thanks again for the clarification.
--
resolution: -> not a bug
stage: -> resolved
status
r n added the comment:
Thanks for the response.
However, if you see, every condition object has their own queue of waiters in
self._waiters, that get notified during notify(), which are different for
not_empty and not_full.
I see a hang very very rarely, like 1/25 times, in my program, which
Change by r n :
--
versions: +Python 3.10, Python 3.9
___
Python tracker
<https://bugs.python.org/issue40907>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by r n :
--
nosy: +rhettinger -r n2
title: cpython/queue.py: put() does not acquire not_empty before notifying on
it -> cpython/lib/queue.py: put() does not acquire not_empty before notifying
on it
___
Python tracker
<
Change by r n :
--
title: cpython/queue.py: put() does not acquire not_empty lock before notifying
on it -> cpython/queue.py: put() does not acquire not_empty before notifying on
it
___
Python tracker
<https://bugs.python.org/issu
Change by r n :
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue40907>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by r n :
--
components: Library (Lib)
nosy: r n2
priority: normal
severity: normal
status: open
title: cpython/queue.py: put() does not acquire not_empty lock before notifying
on it
type: behavior
versions: Python 3.8
___
Python tracker
