The API in general looks nice, but I do have some concens w.r.t. including cffi in the stdlib.
On 26 Feb, 2013, at 16:13, Maciej Fijalkowski <firstname.lastname@example.org> wrote:
> I would like to discuss on the language summit a potential inclusion
> of cffi into stdlib.
1. Why is cffi completely separate from ctypes, instead of layered on top of it? That is, add a utility module to ctypes that can parse C declarations and generate the right ctypes definitions.
2. Cffi has a dependencies on pycparser and that module and its dependencies would therefore also be added to the stdlib (even if they'd be hidden in the cffi package)
3. Cffi basicly contains a (limited) C parser, and those are notoriously hard to get exactly right. Luckily cffi only needs to interpret declarations and not the full language, but even so this can be a risk of subtle bugs.