Mercurial > cpython-lru_cache-weakref

diff Doc/c-api/objbuffer.rst @ 64997:dc4555646e80 3.1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Merged revisions 85082 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r85082 | antoine.pitrou | 2010-09-29 01:39:41 +0200 (mer., 29 sept. 2010) | 4 lines Buffers are not sequence objects (!). Put them in the abstract objects layers instead. ........
author Antoine Pitrou <solipsis@pitrou.net>
date Tue, 28 Sep 2010 23:41:31 +0000
parents 6c8adc200ee0
children 521eac31a893
line wrap: on
line diff
--- a/Doc/c-api/objbuffer.rst	Tue Sep 28 23:05:17 2010 +0000
+++ b/Doc/c-api/objbuffer.rst	Tue Sep 28 23:41:31 2010 +0000
@@ -1,15 +1,16 @@
 .. highlightlang:: c
 
-Old buffer API
---------------
+Old Buffer Protocol
+-------------------
 
 .. deprecated:: 3.0
 
 These functions were part of the "old buffer protocol" API in Python 2.
-In Python 3, these functions are still exposed for ease of porting code.
-They act as a compatibility wrapper around the :ref:`new buffer API
-<bufferobjects>`, but they don't give you control over the lifetime of
-the resources acquired when a buffer is exported.
+In Python 3, this protocol doesn't exist anymore but the functions are still
+exposed to ease porting 2.x code.  They act as a compatibility wrapper
+around the :ref:`new buffer protocol <bufferobjects>`, but they don't give
+you control over the lifetime of the resources acquired when a buffer is
+exported.
 
 Therefore, it is recommended that you call :cfunc:`PyObject_GetBuffer`
 (or the ``y*`` or ``w*`` :ref:`format codes <arg-parsing>` with the
@@ -17,10 +18,6 @@
 an object, and :cfunc:`PyBuffer_Release` when the buffer view can be released.
 
 
-Buffer Protocol
-===============
-
-
 .. cfunction:: int PyObject_AsCharBuffer(PyObject *obj, const char **buffer, Py_ssize_t *buffer_len)
 
    Returns a pointer to a read-only memory location usable as character-based