Skip to content

[3.11] Clarify that every thread has its own default context in contextvars (GH-99246) #100367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
miss-islington merged 1 commit into from
Dec 20, 2022
Merged

[3.11] Clarify that every thread has its own default context in contextvars (GH-99246) #100367

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
Clarify that every thread has its own default context in contextvars (G… 
…H-99246)

(cherry picked from commit cb60b61)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
  • Loading branch information
@pablogsal @miss-islington
pablogsal authored and miss-islington committed Dec 20, 2022
commit ea2af6d1130a44eda303af1a0bb11bc70a2c6d9f
5 changes: 5 additions & 0 deletions Doc/library/contextvars.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,11 @@ Manual Context Management
To get a copy of the current context use the
:func:`~contextvars.copy_context` function.

Every thread will have a different top-level :class:`~contextvars.Context`
object. This means that a :class:`ContextVar` object behaves in a similar
fashion to :func:`threading.local()` when values are assigned in different
threads.

Context implements the :class:`collections.abc.Mapping` interface.

.. method:: run(callable, *args, **kwargs)
Expand Down