On Thu, Mar 3, 2016 at 10:39 AM, Brett Cannon <br...@python.org> wrote: > But I do think the spirit of Victor's idea is worth considering.
+1 > ...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. -eric _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
