From 555cf8e6ee9932c15996a0d127e4b775079f922b Mon Sep 17 00:00:00 2001 From: Will McGugan Date: Sun, 12 Feb 2023 09:40:27 +0000 Subject: [PATCH] comma --- docs/blog/posts/create-task-psa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/posts/create-task-psa.md b/docs/blog/posts/create-task-psa.md index 2cdb9da8d..737316bf2 100644 --- a/docs/blog/posts/create-task-psa.md +++ b/docs/blog/posts/create-task-psa.md @@ -15,7 +15,7 @@ I'm taking a brief break from blogging about [Textual](https://github.com/Textua If you have ever used `asyncio.create_task` you may have created a bug for yourself that is challenging (read *almost impossible*) to reproduce. If it occurs, your code will likely fail in unpredictable ways. -The root cause of this [Heisenbug](https://en.wikipedia.org/wiki/Heisenbug) is that if you don't hold a reference to the task object returned by `create_task` then the task may disappear without warning when Python runs garbage collection. In other words the code in your task will stop running with no obvious indication why. +The root cause of this [Heisenbug](https://en.wikipedia.org/wiki/Heisenbug) is that if you don't hold a reference to the task object returned by `create_task` then the task may disappear without warning when Python runs garbage collection. In other words, the code in your task will stop running with no obvious indication why. This behavior is [well documented](https://docs.python.org/3/library/asyncio-task.html#asyncio.create_task), as you can see from this excerpt (emphasis mine):