Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
The
loopparameter will be removed in version 3.10. As far as I can see,loopparameter is still present in source code, but it is initialized to special valuemixin._marker. It is still in source code probably for backward compatibility reasons. If this is true, we should be able to check iflock._loop is not None, and then check if it matches withself._loop().I run into this issue with 3rd party library
aetcd3which does not explicitly check loop of itsasyncio.Lock/Conditioninstances, butasyncio.locks.Conditiondoes not correctly check for this condition. After monkey-patchingasyncio.Condition, everything works as expected.