On 26 February 2013 18:34, Maciej Fijalkowski email@example.com wrote:
One point which I *think* is correct, but which I don't see noted anywhere. Am I right that cffi needs a C compiler involved in the process, at least somewhere? If that's the case, then it is not a suitable option for at least one use case that I have, writing quick hacks involving the Windows API on a machine that doesn't have a C compiler installed. Another possible case would be writing zip-safe code - if cffi involves a compiled C extension, it won't work when loaded from a zipfile.
cffi does require a C compiler during either runtime or installation, if you use the API. You can still use the ABI level, which is like ctypes, only if you need the extra stuff, you need a C compiler.
Cool, thanks. So if I use it like ctypes, cffi doesn't need a C compiler? That's nice, I never knew that.
I definitely need to try it out. (So many projects, so little time... :-))