Skip to content

Comments

gh-127022: Remove _PyEvalFramePushAndInit_UnTagged#127168

Merged
colesbury merged 1 commit intopython:mainfrom
colesbury:gh-127022-py-eval-frame-untagged
Nov 25, 2024
Merged

gh-127022: Remove _PyEvalFramePushAndInit_UnTagged#127168
colesbury merged 1 commit intopython:mainfrom
colesbury:gh-127022-py-eval-frame-untagged

Conversation

@colesbury
Copy link
Contributor

@colesbury colesbury commented Nov 22, 2024

The interpreter now handles _PyStackRefs pointing to immortal objects without the deferred bit set, so _PyEvalFramePushAndInit_UnTagged is no longer necessary.

The interpreter now handles `_PyStackRef`s pointing to immortal objects
without the deferred bit set, so `_PyEvalFramePushAndInit_UnTagged` is
no longer necessary.
@colesbury colesbury merged commit d3da04b into python:main Nov 25, 2024
@colesbury colesbury deleted the gh-127022-py-eval-frame-untagged branch November 25, 2024 17:24
ebonnal pushed a commit to ebonnal/cpython that referenced this pull request Jan 12, 2025
…127168)

The interpreter now handles `_PyStackRef`s pointing to immortal objects
without the deferred bit set, so `_PyEvalFramePushAndInit_UnTagged` is
no longer necessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants