[issue44800] Code readability: rename interpreter frames to execution frames

2021-08-11 Thread Nick Coghlan
Nick Coghlan added the comment: Mark raised some valid concerns with the proposed naming convention over on the PR: * the proposed names make it sound like there are genuinely two kinds of frame, when the actual relationship is between a frame's data storage and a Python object providing an

[issue44800] Code readability: rename interpreter frames to execution frames

2021-08-01 Thread Nick Coghlan
Nick Coghlan added the comment: PR for this proposed refactoring is now up, with a review requested from Mark: https://github.com/python/cpython/pull/27525/ The PR mostly follows what I originally posted, except that I went with _Py_execution_frame and _PyExecFrame for the struct and typedef

[issue44800] Code readability: rename interpreter frames to execution frames

2021-08-01 Thread Nick Coghlan
Change by Nick Coghlan : -- keywords: +patch pull_requests: +26040 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/27525 ___ Python tracker

[issue44800] Code readability: rename interpreter frames to execution frames

2021-07-31 Thread Nick Coghlan
Nick Coghlan added the comment: As a side effect of working on this, I noticed some changes that are needed to adapt the GDB integration hooks to the new frame state layout. -- nosy: +pablogsal ___ Python tracker

[issue44800] Code readability: rename interpreter frames to execution frames

2021-07-31 Thread Nick Coghlan
Change by Nick Coghlan : -- assignee: -> ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue44800] Code readability: rename interpreter frames to execution frames

2021-07-31 Thread Nick Coghlan
Change by Nick Coghlan : -- dependencies: +Create frame objects lazily when needed ___ Python tracker ___ ___ Python-bugs-list maili

[issue44800] Code readability: rename interpreter frames to execution frames

2021-07-31 Thread Nick Coghlan
New submission from Nick Coghlan : When merging the bpo-44590 changes into my PEP 558 implementation branch, I found it very hard to follow when the code was referring to the new interpreter frames rather than the existing Python frame objects that were historically used for both execution an