A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-July/027183.html below:

[Python-Dev] PEP 298 - the Fixed Buffer Interface

[Python-Dev] PEP 298 - the Fixed Buffer Interface [Python-Dev] PEP 298 - the Fixed Buffer InterfaceThomas Heller thomas.heller@ion-tof.com
Wed, 31 Jul 2002 20:53:23 +0200
I've changed PEP 298 to incorporate the latest changes.
Barry has not yet run pep2html (and I don't want to bother
him too much with this), also I don't know if it makes sense
to post it again in its full length.
So here is the link to view it online in text format:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/nondist/peps/pep-0298.txt?rev=1.4

and this is the checkin message:
-----
The model exposed by the fixed buffer interface was changed:
Retrieving a buffer from an object puts this in a locked state, and a
releasebuffer function must be called to unlock the object again.

Added releasefixedbuffer function slot, and renamed the
get...fixedbuffer functions to acquire...fixedbuffer functions.

Renamed the flag from Py_TPFLAG_HAVE_GETFIXEDBUFFER to
Py_TPFLAG_HAVE_FIXEDBUFFER. (Is the 'fixed buffer' name still useful,
or should we use 'static buffer' instead?)

Added posting date (was posted to c.l.p and python-dev).
-----

Thomas





RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4