From 1abb4a79325b7d7cce5793613d6bf9fa26998c46 Mon Sep 17 00:00:00 2001 From: Sergey Date: Mon, 3 Nov 2025 19:03:56 +0700 Subject: [PATCH] Fixed wrongly mentioned exception in getting-started.md TimeoutException is mentioned in Getting Started, but it actually doesn't exist. Exceeded task timeout will raise TimeoutError, because this is what asyncio.wait.for() does. --- docs/guide/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/getting-started.md b/docs/guide/getting-started.md index 1d9e1c3f..2942612d 100644 --- a/docs/guide/getting-started.md +++ b/docs/guide/getting-started.md @@ -246,7 +246,7 @@ await my_task.kicker().with_labels(timeout=0.3).kiq() ::: caution Cool alert -We use [run_in_executor](https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor) method to run sync functions. Timeouts will raise a TimeoutException, but +We use [run_in_executor](https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor) method to run sync functions. Timeouts will raise a TimeoutError, but synchronous function may not stop from execution. This is a constraint of python. :::