-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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.
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
gh-59956: Clarify Runtime State Status Expectations #101308
Merged
ericsnowcurrently
merged 35 commits into
python:main
from
ericsnowcurrently:pystate-lifecycle-cleanup
Jan 30, 2023
Merged
gh-59956: Clarify Runtime State Status Expectations #101308
ericsnowcurrently
merged 35 commits into
python:main
from
ericsnowcurrently:pystate-lifecycle-cleanup
Jan 30, 2023
+416
−166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ericsnowcurrently
force-pushed
the
pystate-lifecycle-cleanup
branch
from
January 25, 2023 00:46
38fe407
to
8375a8d
Compare
ericsnowcurrently
force-pushed
the
pystate-lifecycle-cleanup
branch
from
January 25, 2023 17:25
fbb4556
to
575a299
Compare
ericsnowcurrently
force-pushed
the
pystate-lifecycle-cleanup
branch
from
January 25, 2023 22:08
575a299
to
6869bfe
Compare
mdboom
pushed a commit
to mdboom/cpython
that referenced
this pull request
Jan 31, 2023
…01308) A PyThreadState can be in one of many states in its lifecycle, represented by some status value. Those statuses haven't been particularly clear, so we're addressing that here. Specifically: * made the distinct lifecycle statuses clear on PyThreadState * identified expectations of how various lifecycle-related functions relate to status * noted the various places where those expectations don't match the actual behavior At some point we'll need to address the mismatches. (This change also includes some cleanup.) python#59956
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A
PyThreadState
can be in one of many states in its lifecycle, represented by some status value. Those statuses haven't been particularly clear, so we're addressing that here. Specifically:PyThreadState
At some point we'll need to address the mismatches.
(This change also includes some cleanup.)