1. Scott Tsai
  2. cffi


Armin Rigo  committed 48c2b9f

Merge the two paragraphs about weave.

  • Participants
  • Parent commits 05aaded
  • 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).
   complete yet) with a reasonable path for other Python implementations like
   IronPython and Jython.
-* Note that this project is **not** about embedding C in Python. Look for
-  ``weave.inline`` for this purpose. This is about calling existing C libraries
+* Note that this project is **not** about embedding executable C code in
+  Python, unlike `Weave`_.  This is about calling existing C libraries
   from Python.
 .. _`LuaJIT's FFI`: http://luajit.org/ext_ffi.html
 .. _`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
+.. _`Weave`: http://www.scipy.org/Weave
 .. _`manually wrap`: `The verification step`_