[Python-Dev] cffi in stdlib
Eli Bendersky
eliben at gmail.com
Tue Feb 26 17:34:59 CET 2013
More information about the Python-Dev mailing list
Tue Feb 26 17:34:59 CET 2013
- Previous message: [Python-Dev] cffi in stdlib
- Next message: [Python-Dev] cffi in stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Feb 26, 2013 at 7:42 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > On Wed, Feb 27, 2013 at 1:13 AM, Maciej Fijalkowski <fijall at gmail.com> > wrote: > > Hello. > > > > I would like to discuss on the language summit a potential inclusion > > of cffi[1] into stdlib. > > I think cffi is well worth considering as a possible inclusion for > Python 3.4. (In particular, I'm a fan of the fact it just uses C > syntax to declare what you're trying to talk to) > I'm cautiously +0.5 because I'd really like to see a strong comparison case being made vs. ctypes. I've used ctypes many times and it was easy and effortless (well, except the segfaults when wrong argument types are declared :-). I'll be really interesting in seeing concrete examples that demonstrate how CFFI is superior. > If I'm reading the dependencies correctly, we would also need to bring > Eli Bendersky's pycparser into the stdlib, correct? (not an objection, > just an observation, although we'd obviously need Eli's explicit > endorsement for that). > Of course I have no problem with this. I obviously signed the contributor agreement by this point ;-) pycparser depends on David Beazley's PLY though, so that will have to be pulled in as well. Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130226/045c6f92/attachment.html>
- Previous message: [Python-Dev] cffi in stdlib
- Next message: [Python-Dev] cffi in stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list