Skip to content

gh-139588: Docs: number the layers in execution model diagram #140445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

gh-139588: Docs: number the layers in execution model diagram #140445

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions Doc/reference/executionmodel.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -412,9 +412,9 @@ its operating system (OS), if there is one. When a program runs,
the conceptual layers of how it runs on the host look something
like this:

| **host machine**
| **process** (global resources)
| **thread** (runs machine code)
| 1. **host machine**
| 2. **process** (global resources)
| 3. **thread** (runs machine code)

Each process represents a program running on the host. Think of each
process itself as the data part of its program. Think of the process'
Expand Down Expand Up @@ -471,12 +471,12 @@ Python Runtime Model
The same conceptual layers apply to each Python program, with some
extra data layers specific to Python:

| **host machine**
| **process** (global resources)
| Python global runtime (*state*)
| Python interpreter (*state*)
| **thread** (runs Python bytecode and "C-API")
| Python thread *state*
| 1. **host machine**
| 2. **process** (global resources)
| 3. Python global runtime (*state*)
| 4. Python interpreter (*state*)
| 5. **thread** (runs Python bytecode and "C-API")
| 6. Python thread *state*

At the conceptual level: when a Python program starts, it looks exactly
like that diagram, with one of each. The runtime may grow to include
Expand Down
Loading