bpo-36373: Deprecate explicit loop parameter in all public asyncio APIs [locks] (GH-13920)
This PR deprecate explicit loop parameters in all public asyncio APIs
This issues is split to be easier to review.
Third step: locks.py
https://bugs.python.org/issue36373
diff --git a/Doc/library/asyncio-sync.rst b/Doc/library/asyncio-sync.rst
index 79f6b02..cc8c29d 100644
--- a/Doc/library/asyncio-sync.rst
+++ b/Doc/library/asyncio-sync.rst
@@ -59,6 +59,9 @@
finally:
lock.release()
+ .. deprecated-removed:: 3.8 3.10
+ The *loop* parameter.
+
.. coroutinemethod:: acquire()
Acquire the lock.
@@ -101,6 +104,10 @@
:meth:`clear` method. The :meth:`wait` method blocks until the
flag is set to *true*. The flag is set to *false* initially.
+
+ .. deprecated-removed:: 3.8 3.10
+ The *loop* parameter.
+
.. _asyncio_example_sync_event:
Example::
@@ -173,6 +180,10 @@
``None``. In the latter case a new Lock object is created
automatically.
+
+ .. deprecated-removed:: 3.8 3.10
+ The *loop* parameter.
+
The preferred way to use a Condition is an :keyword:`async with`
statement::
@@ -269,6 +280,10 @@
internal counter (``1`` by default). If the given value is
less than ``0`` a :exc:`ValueError` is raised.
+
+ .. deprecated-removed:: 3.8 3.10
+ The *loop* parameter.
+
The preferred way to use a Semaphore is an :keyword:`async with`
statement::
@@ -322,6 +337,9 @@
increases the internal counter above the initial *value*.
+ .. deprecated-removed:: 3.8 3.10
+ The *loop* parameter.
+
---------