On 03. 06. 21 1:43, Victor Stinner wrote:
Hi,
What do you think of promoting the pythoncapi_compat project that I'm
introducing below in the "C API: Porting to Python 3.10" section of
What's New In Python 3.10?
Should this project be moved under the GitHub psf organization to have
a more
On Tue, Jun 8, 2021 at 6:02 PM Petr Viktorin wrote:
>
>
> > * Make function PyArg_Parse always raising an exception.
>
> This would break extensions that use the stable ABI.
> (Yes, even starting to raise RuntimeError in 3.10 broke things. And yes,
> it's not strictly an ABI issue, but it has the
On 08. 06. 21 10:05, Serhiy Storchaka wrote:
07.06.21 08:41, Hai Shi пише:
There have an another question. There have many C API defined under
PY_SSIZE_T_CLEAN, for example: _PyArg_Parse_SizeT().
Could we remove or merge them after making PY_SSIZE_T_CLEAN not mandatory?
We should support
07.06.21 08:41, Hai Shi пише:
> There have an another question. There have many C API defined under
> PY_SSIZE_T_CLEAN, for example: _PyArg_Parse_SizeT().
> Could we remove or merge them after making PY_SSIZE_T_CLEAN not mandatory?
We should support binary compatibility to some degree, so there
Irit Katriel via Python-Dev writes:
> Andrei is suggesting to look at each enum value as the set of "bits set to
> 1" in this value, and then apply a set-thoery term to the problem.
> [...] Anyway, I don't know whether this kind of terminology is
> widely accessible.
I think the everyday
