Clarify that every thread has its own default context in contextvars (GH-99246)

(cherry picked from commit cb60b6131bc2bb11c48a15f808914d8b242b9fc5)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>

diff --git a/Doc/library/contextvars.rst b/Doc/library/contextvars.rst
index 08a7c7d74eab97a5957f69260982e130a7a34a5d..0ac2f3d85749b7c48ae5f84dfe5bff39802215ef 100644 (file)
--- a/Doc/library/contextvars.rst
+++ b/Doc/library/contextvars.rst
@@ -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)