GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||
GeezerVison is showing github.com — gh-116098: Clean up frame allocation code and remove the invalid sneaky frame test by gaogaotiantian · Pull Request #116687 · python/cpython Conversation
|
|
Probably not worth backporting. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| // Just pretend that we have an owned, cleared frame so frame_dealloc | ||
| // doesn't make the situation worse: | ||
| f->f_frame = (_PyInterpreterFrame *)f->_f_frame_data; | ||
| f->f_frame->owner = FRAME_CLEARED; |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
We should also remove the corresponding assert(frame->owner != FRAME_CLEARED) statements, especially since FRAME_CLEARED was never a valid member of enum _frameowner (it’s from enum _framestate).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
GH-124148) The `owner` field of `_PyInterpreterFrame` is supposed to be a member of `enum _frameowner`, but `FRAME_CLEARED` is a member of `enum _framestate`. At present, it happens that `FRAME_CLEARED` is not numerically equal to any member of `enum _frameowner`, but that could change in the future. The code that incorrectly assigned `owner = FRAME_CLEARED` was deleted in commit a53cc3f (GH-116687). Remove the incorrect checks for `owner != FRAME_CLEARED` as well.
pythonGH-124148) The `owner` field of `_PyInterpreterFrame` is supposed to be a member of `enum _frameowner`, but `FRAME_CLEARED` is a member of `enum _framestate`. At present, it happens that `FRAME_CLEARED` is not numerically equal to any member of `enum _frameowner`, but that could change in the future. The code that incorrectly assigned `owner = FRAME_CLEARED` was deleted in commit a53cc3f (pythonGH-116687). Remove the incorrect checks for `owner != FRAME_CLEARED` as well.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.