On Thu, Mar 12, 2015 at 12:31 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > On Wed, 11 Mar 2015 23:10:14 +0200 > Maciej Fijalkowski <fij...@gmail.com> wrote: >> > >> > Well, sure. The point is, such bugs are unlikely to appear at a fast >> > rate... Also, I don't understand why libffi issues would affect cffi >> > any less than it affects ctypes, at least in the compiler-less mode of >> > operation. >> >> My point here was only about shipping own libffi vs using the system >> one (and it does affect cffi equally with or without compiler) > > So what? If ctypes used the system libffi as cffi does, it would by > construction be at least portable as cffi is. The only reason the > bundled libffi was patched at some point was to be *more* portable than > vanilla libffi is. > > So, really, I don't see how switching from ctypes to cffi solves any of > this.
You're missing my point. Ripping off the libffi from CPython is a good idea to start with. Maybe deprecating ctypes is *also* a good idea, but it's a separate discussion point. It certainly does not solve the libffi problem. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
