-
-
Notifications
You must be signed in to change notification settings - Fork 32k
AcquirerProxy
object has no attribute locked
#115942
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
stdlib
Python modules in the Lib dir
topic-multiprocessing
type-bug
An unexpected behavior, bug, or error
Comments
We clearly can do that. But, I cannot judge if we should: #115944 I am not a field expert in |
sobolevn
added a commit
that referenced
this issue
Apr 8, 2025
Co-authored-by: mpage <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]>
3.14 will have this new feature :) |
seehwan
pushed a commit
to seehwan/cpython
that referenced
this issue
Apr 16, 2025
…n#115944) Co-authored-by: mpage <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
stdlib
Python modules in the Lib dir
topic-multiprocessing
type-bug
An unexpected behavior, bug, or error
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
According to the documentation, both multiprocessing.Manager.Lock and RLock should be the equivalent of an threading.Lock and RLock, but the underlying AcquirerProxy is missing the implementation of the
.locked()
method to query the state of the lock.E.g.
CPython versions tested on:
3.11, 3.12
Operating systems tested on:
Linux, macOS
Linked PRs
locked
to several multiprocessing locks #115944The text was updated successfully, but these errors were encountered: