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

bpo-46355: What's New: Note that PyFrameObject are private #31032

Merged
merged 1 commit into from Feb 1, 2022

Conversation

@encukou
Copy link
Member

@encukou encukou commented Jan 31, 2022

This adds a slightly more detailed explanation of the change.
The most important point is that the changed/removed fields
were "subject to change" to begin with.

https://bugs.python.org/issue46355

Automerge-Triggered-By: GH:encukou

This adds a slightly more detailed explanation of the change.
The most important point is that the changed/removed fields
were "subject to change" to begin with.
Copy link
Member

@vstinner vstinner left a comment

LGTM. You're right, it's good to remind that the structure is "private".

@vstinner
Copy link
Member

@vstinner vstinner commented Jan 31, 2022

A few lines below, there is "Changes of the PyThreadState structure members". IMO this structure is also private. At least, @markshannon and me want to make it opaque :-)

@encukou
Copy link
Member Author

@encukou encukou commented Jan 31, 2022

Feel free to send a similar PR.
I like to use similar wording as the docs, but I also check the docs of several past versions, to be fair to people that wrote their code long ago.
So for frame I added the "subject to change at any time", but threadstate docs say the members are not "public", so just calling them "private" should work.

@miss-islington miss-islington merged commit a4cb319 into python:main Feb 1, 2022
12 checks passed
@encukou encukou deleted the frame-is-private branch Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants