[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

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

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

STINNER Victor added the comment: Removing the PyFrameObject.f_code member (commit b11a951f16f0603d98de24fee5c023df83ea552c) broke by gevent project: * https://github.com/gevent/gevent/issues/1867 * https://bugs.python.org/issue40421#msg413719 --

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Mark Shannon added the comment: New changeset 0982ded179f280176868c1c4eccf77bf70687816 by Mark Shannon in branch 'main': bpo-44032: Move pointer to code object from frame-object to frame specials array. (GH-26771)

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Change by Mark Shannon : -- pull_requests: +25357 pull_request: https://github.com/python/cpython/pull/26771 ___ Python tracker ___

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

STINNER Victor added the comment: bpo-44184 has been fixed, it was unrelated. Mark fixed a bug in commit af5d497f72ceaf3f207a8aded028607c4c46a993. It seems like all issues are solved, I close the issue. Mark: please set the version field to 3.11 for work in 3.11. Commits: commit

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Pablo Galindo Salgado added the comment: Is the test added here: https://github.com/python/cpython/pull/26274 import ast import builtins import sys import os tree = ast.parse("pass") x = [tree] x.append(x) # Put the cycle somewhere to survive until the *last* GC collection def

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Mark Shannon added the comment: What's the test case, exactly? ref.py for the other issue doesn't crash if I change "func.py" to "ref.py" otherwise it just complains that "func.py" doesn't exist. -- ___ Python tracker

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Pablo Galindo Salgado added the comment: Mark, can you check the failure? Otherwise is going to start failing on the buildbots when we add the test case for the issue Erlend mentions. -- ___ Python tracker

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Change by Pablo Galindo Salgado : -- pull_requests: +24895 pull_request: https://github.com/python/cpython/pull/26291 ___ Python tracker ___

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Change by Mark Shannon : -- pull_requests: +24891 pull_request: https://github.com/python/cpython/pull/26285 ___ Python tracker ___

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Erlend E. Aasland added the comment: cc. Pablo, Victor -- nosy: +pablogsal, vstinner ___ Python tracker ___ ___ Python-bugs-list

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Erlend E. Aasland added the comment: Using Pablo's (or Victor's) reproducer from bpo-44184, I'm getting a crash, apparently because _PyThreadState_PushLocals() is called after PyThreadState_Clear(). In Python/pystate.c interpreter_clear(), we're first calling PyThreadState_Clear() (line

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

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

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Change by Ken Jin : -- nosy: +kj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44032] Function locals and evaluation stack should be stored in a contiguous, per-thread stack

Change by Mark Shannon : -- title: Store locals and evaluation stack should be stored in a contiguous, per-thread stack -> Function locals and evaluation stack should be stored in a contiguous, per-thread stack ___ Python tracker