Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
phrasing for threads & event loops.
  • Loading branch information
anordin95 committed Aug 24, 2025
commit 176814e0a248cdaf3da793d76f15885a51943e46
8 changes: 4 additions & 4 deletions Doc/howto/a-conceptual-overview-of-asyncio.rst
Original file line number Diff line number Diff line change
Expand Up @@ -177,10 +177,10 @@ callback to run it in the event loop's to-do list, that is, collection of jobs).
The recommended way to create tasks is via :func:`asyncio.create_task`.

:mod:`!asyncio` automatically associates tasks with the event loop for you.
In many applications there's only a single thread with the one event loop,
but you can have multiple threads, each with their own event loop.
Each event loop is stored in thread-local storage, making it easy for
:mod:`!asyncio` to associate tasks with the relevant loop for each thread.
Typically there's only one event loop, so that's quite straightforward.
It's uncommon, but some applications use multithreading and :mod:`!asyncio`
together, where there's one event loop per thread, stored in thread-local
Comment thread
anordin95 marked this conversation as resolved.
Outdated
storage.

::

Expand Down