On Tue, Feb 26, 2013 at 5:42 PM, 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) > > 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). Yes, although, depending on the circumstances it's possible to hide it somewhere in cffi and not make it an official stdlib API (then several rules does not apply). It also pulls in some version of ply (or a generated parser). > > There would also be the matter of converting the cffi test suite from > py.test to stdlib unittest. I volunteer to do that, if necessary. > > Cheers, > Nick. > > -- > Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4