[python-committers] Redoing the C API? (was: Call For Participants For The 2016 Python Language Summit)

Eric Snow ericsnowcurrently at gmail.com
Thu Mar 3 12:58:13 EST 2016

On Thu, Mar 3, 2016 at 10:39 AM, Brett Cannon <brett at python.org> wrote:
> But I do think the spirit of Victor's idea is worth considering.


> ...what would we need to do to our C API to make
> it so that anyone following a new API wouldn't be broken if we dropped the
> GIL?

If I recall correctly, this was one key topic that Larry discussed at
the language summit latest year.

>> As for integrating cffi into the stdlib, it seems to be doing fine as a
>> third-party library.
> It is doing fine as an external library, but if something as radical as
> heavily trimming back and/or rewriting the C API occurs then having CFFI in
> the stdlib to evolve with the internal C changes makes sense. I think that's
> where the thought of pulling CFFI in the stdlib stems from.

At least part of the motivation was to deprecate/remove ctypes and
replace it in the stdlib with CFFI.


More information about the python-committers mailing list