Hi all,
I'm having a good discussion with Carl Banks and Greg Ewing over on
python-dev about the buffer interface. We are converging on a pretty
good design, IMHO. If anybody wants to participate in the discussion,
please read the PEP (there are a few things that still need to change)
and
Hi,
I have a specific question and then a general question, and some
minor issues for clarification.
Specifically, regarding the arguments to getbufferproc:
166 format
167address of a format-string (following extended struct
168syntax) indicating what is in each element of
169
Zachary Pincus wrote:
Hi,
Is this saying that either NULL or a pointer to B can be supplied
by getbufferproc to indicate to the caller that the array is unsigned
bytes? If so, is there a specific reason to put the (minor)
complexity of handling this case in the caller's hands,
Is this saying that either NULL or a pointer to B can be supplied
by getbufferproc to indicate to the caller that the array is unsigned
bytes? If so, is there a specific reason to put the (minor)
complexity of handling this case in the caller's hands, instead of
dealing with it internally to
