Skip to content

Commit b12a02b

Browse files
Identify what might be thread-specific state.
1 parent aeca87a commit b12a02b

1 file changed

Lines changed: 3 additions & 6 deletions

File tree

Doc/reference/executionmodel.rst

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -439,12 +439,9 @@ specific to Python::
439439
When a Python program starts, it looks exactly like that, with one
440440
of each. The process has a single global runtime to manage Python's
441441
global resources. Each Python thread has all the state it needs to run
442-
Python code (and use any supported C-API) in its OS thread.
443-
444-
.. , including its stack of call frames.
445-
446-
.. If the program uses coroutines (async) then the thread will end up
447-
juggling multiple stacks.
442+
Python code (and use any supported C-API) in its OS thread. Depending
443+
on the implementation, this probably includes the current exception
444+
and the Python call stack.
448445

449446
In between the global runtime and the thread(s) lies the interpreter.
450447
It completely encapsulates all of the non-global runtime state that the

0 commit comments

Comments
 (0)