Uh oh!
There was an error while loading. Please reload this page.
gh-134939: Fill Out the concurrent.interpreters Docs - #135902
Conversation
auvipy
left a comment
There was a problem hiding this comment.
I'm not sure if the double spaces were intended or not. so suggested some edits....
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
StanFromIreland
commented
Jun 25, 2025
@auvipy I presume Eric is using emacs, the double spaces are fine and conform to many technical writing style guides IIRC. You will find many occurrences throughout out the docs. |
auvipy
commented
Jun 25, 2025
Interesting! Didn’t know that to be honest |
ericsnowcurrently
commented
Jun 25, 2025
Using double space between sentences is fairly standard. Traditionally the practice was meant to introduce a stronger visual separation between sentences, to help readers identify the boundary. Using a single space is a relatively recent practice, one that reflects an assumption that the software which renders (lays out) the text, like a browser, will render the inter-sentence boundary sufficiently distinctly. However, in my experience that isn't what actually happens most of the time. (Plus, the same software could just as easily detect the double space and render it how it likes.) Furthermore, text editors in particular don't necessarily follow this practice. For example, I use a fixed-width font in my terminal. Ultimately, any time the the text is rendered naively this way, it presents a readability challenge. Thus, I avoid using a single space between sentences. |
StanFromIreland
commented
Jun 25, 2025
Very, historically started when type writers where introduced :-) |
| Running mostly involves switching to an interpreter (in the current | ||
| thread) and calling a function in that execution context. |
There was a problem hiding this comment.
I'd like a reference to the "Runtime Components" section after #135944 is landed, regarding the OS thread?
There was a problem hiding this comment.
Places like these are a large part of why I opened that issue. 😄
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| * :class:`float` | ||
| * :class:`tuple` (of similarly supported objects) | ||
| There is a small number of Python types that actually share mutable |
There was a problem hiding this comment.
| There is a small number of Python types that actually share mutable | |
| There are a small number of Python types that actually share mutable |
There was a problem hiding this comment.
The subject of the verb is "a small number", which is singular. Otherwise, I'd agree that "There are Python types that..." would be correct.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: neonene <53406459+neonene@users.noreply.github.com>
ericsnowcurrently
commented
Jun 27, 2025
Unless there are any major objections, I'd like to land this today;, I have a "multiple interpreters HOWTO" branch, on top of this change, that I want to put up for review. If there are little things to tweak, I think we can take care of that in a follow-up PR. |
Uh oh!
There was an error while loading. Please reload this page.
Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
GH-136141 is a backport of this pull request to the 3.14 branch. |
📚 Documentation preview 📚: https://cpython-previews--135902.org.readthedocs.build/