[pypy-commit] cffi default: move up this warning

arigo noreply at buildbot.pypy.org
Wed May 20 09:08:31 CEST 2015


Author: Armin Rigo <arigo at tunes.org>
Branch: 
Changeset: r2060:49050def179f
Date: 2015-05-20 09:09 +0200
http://bitbucket.org/cffi/cffi/changeset/49050def179f/

Log:	move up this warning

diff --git a/doc/source/cdef.rst b/doc/source/cdef.rst
--- a/doc/source/cdef.rst
+++ b/doc/source/cdef.rst
@@ -481,6 +481,12 @@
 for large projects where one CFFI-based interface depends on some
 types declared in a different CFFI-based interface.
 
+*Note that you should only use one ffi object per library; the intended
+usage of ffi.include() is if you want to interface with several
+inter-dependent libraries.*  For only one library, make one ``ffi``
+object.  (You can write several ``cdef()`` calls over the same ``ffi``
+from several Python files, if one file would be too large.)
+
 For out-of-line modules, the ``ffi.include(other_ffi)`` line should
 occur in the build script, and the ``other_ffi`` argument should be
 another FFI that comes from another build script.  When the two build
@@ -499,11 +505,6 @@
 In ABI mode, these must be accessed via the original ``other_lib``
 object returned by the ``dlopen()`` method on ``other_ffi``.
 
-*Note that you should only use one ffi object per library; the
-intended usage of ffi.include() is if you want to interface with
-several inter-dependent libraries.*  For only one library, make one
-``ffi`` object.
-
 
 ffi.cdef() limitations
 ----------------------


More information about the pypy-commit mailing list