Fix patchcheck for `asyncio.tasks` (#108159)

diff --git a/Lib/asyncio/tasks.py b/Lib/asyncio/tasks.py
index 75dd3cb6c2e9874d847a1c650085be3e3030b610..edc64fda2a6ad6b12edbeb0210e37a1d4ec02015 100644 (file)
--- a/Lib/asyncio/tasks.py
+++ b/Lib/asyncio/tasks.py
@@ -935,21 +935,21 @@ def run_coroutine_threadsafe(coro, loop):
 def create_eager_task_factory(custom_task_constructor):
     """Create a function suitable for use as a task factory on an event-loop.
 
-           Example usage:
+        Example usage:
 
-               loop.set_task_factory(
-                   asyncio.create_eager_task_factory(my_task_constructor))
+            loop.set_task_factory(
+                asyncio.create_eager_task_factory(my_task_constructor))
 
-           Now, tasks created will be started immediately (rather than being first
-           scheduled to an event loop). The constructor argument can be any callable
-           that returns a Task-compatible object and has a signature compatible
-           with `Task.__init__`; it must have the `eager_start` keyword argument.
+        Now, tasks created will be started immediately (rather than being first
+        scheduled to an event loop). The constructor argument can be any callable
+        that returns a Task-compatible object and has a signature compatible
+        with `Task.__init__`; it must have the `eager_start` keyword argument.
 
-           Most applications will use `Task` for `custom_task_constructor` and in
+        Most applications will use `Task` for `custom_task_constructor` and in
         this case there's no need to call `create_eager_task_factory()`
         directly. Instead the  global `eager_task_factory` instance can be
         used. E.g. `loop.set_task_factory(asyncio.eager_task_factory)`.
-           """
+        """
 
     def factory(loop, coro, *, name=None, context=None):
         return custom_task_constructor(