1. Python CFFI
  2. Untitled project
  3. cffi


Armin Rigo  committed 12f0451

- compare with weave
- comment about pypy

  • Participants
  • Parent commits a071531
  • Branches default

Comments (0)

Files changed (1)

File doc/source/index.rst

View file
  • Ignore whitespace
   (ctypes_ works at the ABI level, whereas `native C extensions`_
   work at the API level.)
+* This is not `weave`_: it's the other way around.  Weave is about
+  writing some C code to execute inline in the Python program; in CFFI
+  you write the *declarations* in C syntax but the execution of your
+  program is in Python.
 * We try to be complete.  For now some C99 constructs are not supported,
   but all C89 should be, including macros (and including macro "abuses",
   which you can `manually wrap`_ in saner-looking C functions).
 .. _`CPython native C extensions`: http://docs.python.org/extending/extending.html
 .. _`native C extensions`: http://docs.python.org/extending/extending.html
 .. _`ctypes`: http://docs.python.org/library/ctypes.html
+.. _`weave`: http://www.scipy.org/Weave
 .. _`manually wrap`: `The verification step`_
 platform as well as on Win32.  There are some Windows-specific issues
-It currently supports CPython 2.x.  Support for PyPy is coming soon.
-Support for CPython 3.x should not be too hard.
+It currently supports CPython 2.x.  Support for CPython 3.x should not
+be too hard.  Support for PyPy is coming soon.  (In fact, the authors of
+CFFI are also on the PyPy team; we plan to make it the first (and
+fastest) choice for PyPy.)