[Python-Dev] Re: Making PY_SSIZE_T_CLEAN not mandatory.

2021-06-18 Thread Guido van Rossum
Can you elaborate on that use case? Which two applications are you thinking of, and what was your goal in driving them? This sounds interesting but I haven’t encountered this myself. On Fri, Jun 18, 2021 at 09:44 Baptiste Carvello < devel2...@baptiste-carvello.net> wrote: > Le 18/06/2021 à

[Python-Dev] Summary of Python tracker Issues

2021-06-18 Thread Python tracker
ACTIVITY SUMMARY (2021-06-11 - 2021-06-18) 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: open7446 (-11) closed 48743 (+67) total 56189 (+56) Open issues

[Python-Dev] Re: Making PY_SSIZE_T_CLEAN not mandatory.

2021-06-18 Thread Baptiste Carvello
Le 18/06/2021 à 08:50, Paul Moore a écrit : > > IMO it doesn't. However for certain applications (the sort of thing I > was referring to) - where the user is writing their own scripts and > the embedding API is used merely to expose an interface to the Python > language, dynamically linking to

[Python-Dev] Re: Making PY_SSIZE_T_CLEAN not mandatory.

2021-06-18 Thread Paul Moore
On Fri, 18 Jun 2021 at 01:57, Guido van Rossum wrote: > > I don’t see how the stable ABI works as a substitute for vendoring Python. A > lot of other things can still vary even when the C API remains the same! > (E.g. syntax, and stdlib behavior.) IMO it doesn't. However for certain