[3.12] Fix patchcheck for `asyncio.tasks` (GH-108159) (#108160)

Fix patchcheck for `asyncio.tasks` (GH-108159)
(cherry picked from commit b1e5d2c601bbd3d435b60deef4818f3622bdfca3)

Co-authored-by: Kumar Aditya <kumaraditya@python.org>

1 files changed, 9 insertions, 9 deletions

diff --git a/Lib/asyncio/tasks.py b/Lib/asyncio/tasks.py
index 8d5bde0..152c9f8 100644
--- a/Lib/asyncio/tasks.py
+++ b/Lib/asyncio/tasks.py
@@ -944,21 +944,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(