From f56468af8b3789d0e20be30715c20ac1bb367641 Mon Sep 17 00:00:00 2001 From: Kumar Aditya Date: Sat, 23 Nov 2024 13:19:14 +0530 Subject: [PATCH] improve comment --- Modules/_asynciomodule.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Modules/_asynciomodule.c b/Modules/_asynciomodule.c index aab57603a6a541..362d55ad97a4bb 100644 --- a/Modules/_asynciomodule.c +++ b/Modules/_asynciomodule.c @@ -2155,8 +2155,8 @@ enter_task(asyncio_state *state, PyObject *loop, PyObject *task) // memory reads and logic, as Python's dict is a notoriously complex // and ever-changing data structure. // - // So the actual solution is to put a reference to the currently - // running asyncio Task to the interpreter thread state (we already + // So the easier solution is to put a strong reference of the currently + // running `asyncio.Task` to the interpreter thread state (we already // have some asyncio state there.) _PyThreadStateImpl *ts = (_PyThreadStateImpl *)_PyThreadState_GET(); if (ts->asyncio_running_loop == loop) { @@ -2172,7 +2172,7 @@ enter_task(asyncio_state *state, PyObject *loop, PyObject *task) // // That said, we still want to make sure we don't end up in // a broken state, so we check that we're in the correct thread - // by comparing the *loop* argument to the event loop set + // by comparing the *loop* argument to running event loop // in the current thread. If they match we know we're in the // right thread, as asyncio event loops don't change threads. assert(ts->asyncio_running_task == NULL);