Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

gh-59956: Clarify Runtime State Status Expectations#101308

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@ericsnowcurrently
Copy link
Member

@ericsnowcurrentlyericsnowcurrently commentedJan 25, 2023
edited by bedevere-bot
Loading

APyThreadState 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 onPyThreadState
  • 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.)

@ericsnowcurrentlyericsnowcurrently marked this pull request as ready for reviewJanuary 30, 2023 18:56
@ericsnowcurrentlyericsnowcurrently merged commite11fc03 intopython:mainJan 30, 2023
@ericsnowcurrentlyericsnowcurrently deleted the pystate-lifecycle-cleanup branchJanuary 30, 2023 19:07
mdboom pushed a commit to mdboom/cpython that referenced this pull requestJan 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 behaviorAt some point we'll need to address the mismatches.(This change also includes some cleanup.)python#59956
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ericsnowcurrently@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp