[issue44590] Create frame objects lazily when needed

STINNER Victor added the comment: I created bpo-46836: "[C API] Move PyFrameObject to the internal C API". -- nosy: +vstinner ___ Python tracker ___

[issue44590] Create frame objects lazily when needed

Nick Coghlan added the comment: The newly linked pull request isn't actually for this ticket, it's for bpo-44800, a follow-up refactoring proposal related to the variable, struct field, and API naming schemes used for the new lighter weight execution frames. However, the commit message and

[issue44590] Create frame objects lazily when needed

Change by Nick Coghlan : -- nosy: +ncoghlan nosy_count: 3.0 -> 4.0 pull_requests: +26041 pull_request: https://github.com/python/cpython/pull/27525 ___ Python tracker ___

[issue44590] Create frame objects lazily when needed

Change by Mark Shannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44590] Create frame objects lazily when needed

Mark Shannon added the comment: New changeset ae0a2b756255629140efcbe57fc2e714f0267aa3 by Mark Shannon in branch 'main': bpo-44590: Lazily allocate frame objects (GH-27077) https://github.com/python/cpython/commit/ae0a2b756255629140efcbe57fc2e714f0267aa3 --

[issue44590] Create frame objects lazily when needed

Change by Mark Shannon : -- keywords: +patch pull_requests: +25626 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27077 ___ Python tracker ___

[issue44590] Create frame objects lazily when needed

New submission from Mark Shannon : In https://bugs.python.org/issue44032 we moved most of the data in the frame stack, that is the locals, stack, and "specials" (globals, builtins, code etc), from the heap allocated stack to a (mostly) contiguous array in memory. That offered some speed up