[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset fb2c7c4afbab0514352ab0246b0c0cc85d1bba53 by Victor Stinner in branch 'master': bpo-40513: _xxsubinterpreters.run_string() releases the GIL (GH-19944) https://github.com/python/cpython/commit/fb2c7c4afbab0514352ab0246b0c0cc85d1bba53 --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 7be4e350aadf93c4be5c97b7291d0db2b6bc1dc4 by Victor Stinner in branch 'master': bpo-40513: Per-interpreter GIL (GH-19943) https://github.com/python/cpython/commit/7be4e350aadf93c4be5c97b7291d0db2b6bc1dc4 --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 0dd5e7a718997da2026ed64fe054dc36cae4fee7 by Victor Stinner in branch 'master': bpo-40513: new_interpreter() init GIL earlier (GH-19942) https://github.com/python/cpython/commit/0dd5e7a718997da2026ed64fe054dc36cae4fee7 --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19258 pull_request: https://github.com/python/cpython/pull/19944 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19257 pull_request: https://github.com/python/cpython/pull/19943 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19256 pull_request: https://github.com/python/cpython/pull/19942 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: > From a user perspective, does it make sense to have a different > recursion_limit per interpreter? Yes, I think so. Someone might use a lower limit to run a template rendering engine or "unsafe" code. Well, it's not hard to find random usage for

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: > FWIW, I think it would make sense to keep "signals_pending" under > _PyRuntimeState rather than moving it to PyInterpreterState. Oh right. I forgot about the details. I reverted my change, but this time I added a comment to prevent me to write the same

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 299b8c61e9d1a42b929b8deb1b05067876e191e6 by Victor Stinner in branch 'master': Revert "bpo-40513: Per-interpreter signals pending (GH-19924)" (GH-19932) https://github.com/python/cpython/commit/299b8c61e9d1a42b929b8deb1b05067876e191e6

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Eric Snow added the comment: If this issue covers the GIL (which it seems to) then I'd expect _PyRuntimeState.gilstate to be handled here too. -- ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Eric Snow added the comment: >From a user perspective, does it make sense to have a different >recursion_limit per interpreter? I don't see a problem with it. However, >does it make sense to also keep a global value that we default to when a >per-interpreter value is not set? I think it

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Eric Snow added the comment: FWIW, I think it would make sense to keep "signals_pending" under _PyRuntimeState rather than moving it to PyInterpreterState. Signals are only handled by the main interpreter (in its main thread). Even though "signals_pending" is useful to only one interpreter

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19247 pull_request: https://github.com/python/cpython/pull/19932 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 4e30ed3af06ae655f4cb8aad8cba21f341384250 by Victor Stinner in branch 'master': bpo-40513: Per-interpreter recursion_limit (GH-19929) https://github.com/python/cpython/commit/4e30ed3af06ae655f4cb8aad8cba21f341384250 --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: For signals_pending, see also: bpo-40010 "Inefficient signal handling in multithreaded applications" which added _Py_ThreadCanHandleSignals() and _Py_ThreadCanHandlePendingCalls() functions. -- ___ Python tracker

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19244 pull_request: https://github.com/python/cpython/pull/19929 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by hai shi : -- nosy: +shihai1991 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 0b1e3307e24b0af45787ab6456535b8346e0239a by Victor Stinner in branch 'master': bpo-40513: Per-interpreter gil_drop_request (GH-19927) https://github.com/python/cpython/commit/0b1e3307e24b0af45787ab6456535b8346e0239a --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: Python/ceval.c also has "int _Py_CheckRecursionLimit = Py_DEFAULT_RECURSION_LIMIT;". _Py_CheckRecursiveCall() has this comment: /* Needed for ABI backwards-compatibility (see bpo-31857) */ _Py_CheckRecursionLimit = recursion_limit; I converted

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- pull_requests: +19242 pull_request: https://github.com/python/cpython/pull/19927 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: New changeset 4e01946cafca0cf49f796c3118e0d65237bcad69 by Victor Stinner in branch 'master': bpo-40513: Per-interpreter signals pending (GH-19924) https://github.com/python/cpython/commit/4e01946cafca0cf49f796c3118e0d65237bcad69 --

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

Change by STINNER Victor : -- keywords: +patch pull_requests: +19239 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19924 ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

STINNER Victor added the comment: See also: https://github.com/ericsnowcurrently/multi-core-python/issues/34 -- ___ Python tracker ___

[issue40513] Move _PyRuntimeState.ceval to PyInterpreterState

New submission from STINNER Victor : To get one GIL per interpreter (bpo-40512), remaining _PyRuntimeState.ceval members should be moved to PyInterpreterState.ceval. The work started in bpo-39984 with ceval "pending calls" and ceval "eval breaker". There are 4 remaining fields: struct