Author: Armin Rigo <[email protected]> Branch: Changeset: r2747:8ee16fdadf92 Date: 2016-08-24 17:34 +0200 http://bitbucket.org/cffi/cffi/changeset/8ee16fdadf92/
Log: update whatsnew diff --git a/doc/source/cdef.rst b/doc/source/cdef.rst --- a/doc/source/cdef.rst +++ b/doc/source/cdef.rst @@ -529,9 +529,7 @@ the same version of CPython x.y). However, the standard ``distutils`` package will still produce a file called e.g. ``NAME.cpython-35m-x86_64-linux-gnu.so``. You can manually rename it to -``NAME.abi3.so``. There are certainly other ways to compile the C code -that produce directly the correct file name, but I know of no -widely-used solution. +``NAME.abi3.so``, or use setuptools version 26 or later. **ffibuilder.compile(tmpdir='.', verbose=False):** explicitly generate the .py or .c file, diff --git a/doc/source/whatsnew.rst b/doc/source/whatsnew.rst --- a/doc/source/whatsnew.rst +++ b/doc/source/whatsnew.rst @@ -6,6 +6,13 @@ v1.8 ==== +* CPython 3.x: experimental: the generated C extension modules now use + the "limited API", which means that, as a compiled .so/.dll, it should + work directly on any version of CPython >= 3.2. The name produced by + distutils is still version-specific. To get the version-independent + name, you can rename it manually to ``NAME.abi3.so``, or use the very + recent setuptools 26. + * Removed the restriction that ``ffi.from_buffer()`` cannot be used on byte strings. Now you can get a ``char *`` out of a byte string, which is valid as long as the string object is kept alive. (But _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
