Skip to content

Commit e5f1d18

Browse files
committed
Change the glossary definition a little bit.
1 parent 8ce3d7d commit e5f1d18

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

Doc/glossary.rst

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,11 @@ Glossary
136136

137137
A :term:`thread state` that is :term:`active <current thread state>`
138138
for the current thread. If no thread state is attached, then the
139-
:term:`current thread state` is ``NULL``.
139+
:term:`current thread state` is ``NULL``. Attempting to call Python
140+
without an attached thread state will generally result in a fatal error.
141+
142+
A thread state can be attached and detached explicitly by the user, or
143+
implicitly by the interpreter.
140144

141145
On most builds of Python, having an attached thread state means that the
142146
caller holds the :term:`GIL` for the current interpreter.
@@ -1303,8 +1307,10 @@ Glossary
13031307

13041308
thread state
13051309
In Python's C API, a thread state is a structure that holds
1306-
information about the current thread. A thread state must be
1307-
:term:`active <current thread state>` for the current thread in order to call most of the C API.
1310+
information about the current thread. A thread state can be
1311+
attached or detached. An :term:`attached thread state` is required
1312+
to call most of the C API, unless a function explicitly documents
1313+
otherwise.
13081314

13091315
See :ref:`Thread State and the Global Interpreter Lock <threads>` for more
13101316
information.

0 commit comments

Comments
 (0)