Commit949fd5f

committed

Clarify that every thread has its own default context in contextvars

1 parent5ff81da commit949fd5fCopy full SHA for 949fd5f

File tree

-0

lines changed

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
@@ -14,6 +14,12 @@ and work with Context Variables. The :func:`~contextvars.copy_context`
`14`	`14`	function and the:class:`~contextvars.Context` class should be used to
`15`	`15`	`manage the current context in asynchronous frameworks.`
`16`	`16`
	`17`	`+..note::`
	`18`	`+ By default, every thread will have a different default`
	`19`	+:class:`~contextvars.Context`. This means that a
	`20`	+:class:`~contextvars.ContextVar` can generally be used as a drop-in
	`21`	+ replacement for a:func:`threading.local` variable.
	`22`	`+`
`17`	`23`	`Context managers that have state should use Context Variables`
`18`	`24`	instead of:func:`threading.local()` to prevent their state from
`19`	`25`	`bleeding to other code unexpectedly, when used in concurrent code.`

Comments

(0)