Skip to content
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

PEP 667: Update to account for changes to PEP 558 and feedback from Nick. #2180

Merged
merged 2 commits into from
Dec 6, 2021

Conversation

markshannon
Copy link
Member

No description provided.

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

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

Sure. Did @ncoghlan land his changes to PEP 558 yet?

@markshannon markshannon merged commit 91b9f68 into python:main Dec 6, 2021
@ncoghlan
Copy link
Contributor

ncoghlan commented Dec 22, 2021

I thought PEP 558 was updated in early November, but it turns out I failed to actually merge the PR. That oversight is fixed now: #2124

The comparison section in PEP 667 will need updates to account for those changes (as PEP 558 now offers the same Python level semantics as 667 - anything that suggests otherwise is an editing oversight in the last update).

The implementation is lagging a bit as I'm waiting for @markshannon to reply on python/cpython#27525 (review) (his criticism of my "execution frame" naming idea is both valid and equally applicable to the current "interpreter frame" naming, so I'd like to rename that struct to "frame data" before merging it with the PEP 558 implementation)

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.

4 participants