Author: Armin Rigo <[email protected]> Branch: Changeset: r3183:378b0cdeadb5 Date: 2019-01-27 09:27 +0100 http://bitbucket.org/cffi/cffi/changeset/378b0cdeadb5/
Log: tweak docs diff --git a/doc/source/ref.rst b/doc/source/ref.rst --- a/doc/source/ref.rst +++ b/doc/source/ref.rst @@ -608,8 +608,9 @@ **ffi.release(cdata)**: release the resources held by a cdata object from ``ffi.new()``, ``ffi.gc()``, ``ffi.from_buffer()`` or ``ffi.new_allocator()()``. The cdata object must not be used afterwards. -The regular destructor of the cdata object releases the same resources, -but this allows the operation to occur at a known time. +The normal Python destructor of the cdata object releases the same resources, +but this allows the releasing to occur at a known time, as opposed as at an +unspecified point in the future. *New in version 1.12.* ``ffi.release(cdata)`` is equivalent to ``cdata.__exit__()``, which means that diff --git a/doc/source/whatsnew.rst b/doc/source/whatsnew.rst --- a/doc/source/whatsnew.rst +++ b/doc/source/whatsnew.rst @@ -23,14 +23,13 @@ * CPython 2.x: ``ffi.dlopen()`` failed with non-ascii file names on Posix -* ``ffi.from_buffer()`` takes two new arguments: an optional *first* argument - gives the array type of the result; and the keyword argument - ``require_writable`` can ask the object passed in to raise an exception if - it is read-only. +* ``ffi.from_buffer()`` takes a new optional *first* argument that gives + the array type of the result. It also takes an optional keyword argument + ``require_writable`` to refuse read-only Python buffers. * ``ffi.new()``, ``ffi.gc()`` or ``ffi.from_buffer()`` cdata objects can now be released at known times, either by using the ``with`` - keyword or be calling the new ``ffi.release()``. + keyword or by calling the new ``ffi.release()``. v1.11.5 _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
