Skip to content

Conversation

ericsnowcurrently
Copy link
Member

@ericsnowcurrently ericsnowcurrently commented Jun 25, 2025

The section provides a brief overview of the Python runtime's execution environment.

This is meant to be implementation agnostic, If that doesn't hold true then we should take a different approach.


📚 Documentation preview 📚: https://cpython-previews--135945.org.readthedocs.build/

@ericsnowcurrently
Copy link
Member Author

FWIW, I'm going to open a DPO thread about this addition before merging, to make sure there's sufficient visibility.

@ericsnowcurrently
Copy link
Member Author

Copy link
Contributor

@jeff5 jeff5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very much support the idea of clearly explaining this. I hope the comments are not too ignorant to be useful.

@ericsnowcurrently
Copy link
Member Author

@jeff5
Copy link
Contributor

jeff5 commented Jul 1, 2025

Thanks @ericsnowcurrently for giving this so much thought. All good by me. Ping me if I ought to signify this myself by resolving each.

@ericsnowcurrently
Copy link
Member Author

FYI, given the nice break I had from this change, I came back to with fresh eyes and found ways I think it could be more clear.

@ericsnowcurrently
Copy link
Member Author

@ncoghlan, do you have any thoughts about this new section?

FWIW, my intent is to keep the section implementation-agnostic, even if some of the terminology comes from CPython. The described concepts are meant to be conceptual, even if they correspond closely to concrete implementation details.

@ericsnowcurrently
Copy link
Member Author

I have toyed with the idea of specifying what it means to "call into Python", but that can be addressed separately, if at all.

Copy link
Contributor

@ncoghlan ncoghlan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Couple of minor comments inline, but nothing I'd consider merge blocking.

@ncoghlan
Copy link
Contributor

I have toyed with the idea of specifying what it means to "call into Python", but that can be addressed separately, if at all.

If you tried to cover all the subtleties, I think you'd end up with something three times as long that was actually worse for the primary topic you're aiming to address (giving folks that aren't already familiar with the way threads and processes work in general the gist of how they work for Python in particular).

@jeff5
Copy link
Contributor

jeff5 commented Oct 2, 2025

This is really helpful to my understanding, especially of the possible multiplicity (or not) of relationships amongst the separate concepts. It's hard to express this kind of thing accurately and independent of a particular implementation, but I think you have. Thanks for the hard work.

@ericsnowcurrently ericsnowcurrently merged commit 46a1f0a into python:main Oct 2, 2025
27 checks passed
@github-project-automation github-project-automation bot moved this from Todo to Done in Docs PRs Oct 2, 2025
@miss-islington-app
Copy link

Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖

@ericsnowcurrently ericsnowcurrently deleted the exec-model-runtime-components branch October 2, 2025 15:13
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 2, 2025
…Model Docs (pythongh-135945)

The section provides a brief overview of the Python runtime's execution environment.  It is meant to be implementation agnostic,
(cherry picked from commit 46a1f0a)

Co-authored-by: Eric Snow <[email protected]>
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 2, 2025
…Model Docs (pythongh-135945)

The section provides a brief overview of the Python runtime's execution environment.  It is meant to be implementation agnostic,
(cherry picked from commit 46a1f0a)

Co-authored-by: Eric Snow <[email protected]>
@bedevere-app
Copy link

bedevere-app bot commented Oct 2, 2025

GH-139509 is a backport of this pull request to the 3.14 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.14 bugs and security fixes label Oct 2, 2025
@bedevere-app
Copy link

bedevere-app bot commented Oct 2, 2025

GH-139510 is a backport of this pull request to the 3.13 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.13 bugs and security fixes label Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants