Skip to content

Commit daad226

Browse files
authored
Number the layers in execution model diagram
1 parent 0c01090 commit daad226

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

Doc/reference/executionmodel.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -412,9 +412,9 @@ its operating system (OS), if there is one. When a program runs,
412412
the conceptual layers of how it runs on the host look something
413413
like this:
414414

415-
| **host machine**
416-
| **process** (global resources)
417-
| **thread** (runs machine code)
415+
| 1. **host machine**
416+
| 2. **process** (global resources)
417+
| 3. **thread** (runs machine code)
418418
419419
Each process represents a program running on the host. Think of each
420420
process itself as the data part of its program. Think of the process'
@@ -471,12 +471,12 @@ Python Runtime Model
471471
The same conceptual layers apply to each Python program, with some
472472
extra data layers specific to Python:
473473

474-
| **host machine**
475-
| **process** (global resources)
476-
| Python global runtime (*state*)
477-
| Python interpreter (*state*)
478-
| **thread** (runs Python bytecode and "C-API")
479-
| Python thread *state*
474+
| 1. **host machine**
475+
| 2. **process** (global resources)
476+
| 3. Python global runtime (*state*)
477+
| 4. Python interpreter (*state*)
478+
| 5. **thread** (runs Python bytecode and "C-API")
479+
| 6. Python thread *state*
480480
481481
At the conceptual level: when a Python program starts, it looks exactly
482482
like that diagram, with one of each. The runtime may grow to include

0 commit comments

Comments
 (0)