From 6db43fdb3bbe3fc470f51f3674818f925b8f130c Mon Sep 17 00:00:00 2001 From: Antoine Pitrou Date: Tue, 28 Sep 2010 21:53:46 +0000 Subject: Merged revisions 85075 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r85075 | antoine.pitrou | 2010-09-28 23:52:30 +0200 (mar., 28 sept. 2010) | 3 lines Discourage use of the old buffer API funcs ........ --- Doc/c-api/objbuffer.rst | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/Doc/c-api/objbuffer.rst b/Doc/c-api/objbuffer.rst index 0973aad..ef4e4ea 100644 --- a/Doc/c-api/objbuffer.rst +++ b/Doc/c-api/objbuffer.rst @@ -1,6 +1,21 @@ .. highlightlang:: c -.. _abstract-buffer: +Old buffer API +-------------- + +.. 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 +`, 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 ` with the +:cfunc:`PyArg_ParseTuple` family of functions) to get a buffer view over +an object, and :cfunc:`PyBuffer_Release` when the buffer view can be released. + Buffer Protocol =============== -- cgit v0.12