[Python-Dev] Re: Should we pass tstate in the VECTORCALL calling convention before making it public?

2020-01-10 Thread Victor Stinner
Le ven. 10 janv. 2020 à 20:44, Jim J. Jewett a écrit : > Is work this summarized somewhere like a PEP? This work is related to: PEP 554 -- Multiple Interpreters in the Stdlib https://www.python.org/dev/peps/pep-0554/ Victor ___ Python-Dev mailing

[Python-Dev] Re: Should we pass tstate in the VECTORCALL calling convention before making it public?

2020-01-10 Thread Jim J. Jewett
Victor Stinner wrote: > I started to modify Python internals to pass explicitly the Python > thread state ("tstate") to internal C a functions: Is work this summarized somewhere like a PEP? > https://vstinner.github.io/cpython-pass-tstate.html describes the motivation, but not the details on

[Python-Dev] Summary of Python tracker Issues

2020-01-10 Thread Python tracker
ACTIVITY SUMMARY (2020-01-03 - 2020-01-10) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7251 (+24) closed 43792 (+66) total 51043 (+90) Open issues

[Python-Dev] Re: Should we pass tstate in the VECTORCALL calling convention before making it public?

2020-01-10 Thread Steve Dower
On 09Jan2020 1659, Victor Stinner wrote: Le jeu. 9 janv. 2020 à 19:33, Steve Dower a écrit : Requiring an _active_ Python thread (~GIL held) to only run on a single OS thread is fine, but tying it permanently to a single OS thread makes things very painful. (Of course, this isn't the only

[Python-Dev] Re: Why doesn't venv also install python3*-config?

2020-01-10 Thread Victor Stinner
Le jeu. 9 janv. 2020 à 17:19, Xavier de Gaye a écrit : > A cross-compilation means that there is probably no build framework on the > target platform and therefore the build configuration of the > cross-compilation of Python is not very useful there. Ok, so the shell script python-config is