Josiah Carlson wrote:
> Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> Josiah Carlson wrote:
>>> "Travis E. Oliphant" <[EMAIL PROTECTED]> wrote:
The buffer interface should allow discontiguous memory areas to
share standard striding information. However, consumers that do
no
Greg Ewing <[EMAIL PROTECTED]> wrote:
>
> Nick Coghlan wrote:
>
> > I think the point is for there to be something in the standard library
> > or Python core that makes it easy for a consumer to *copy* the data to a
> > contiguous memory segment in the event the consumer can't directly
> > ha
Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Josiah Carlson wrote:
> > "Travis E. Oliphant" <[EMAIL PROTECTED]> wrote:
> >> The buffer interface should allow discontiguous memory areas to
> >> share standard striding information. However, consumers that do
> >> not want to deal with stri
Nick Coghlan wrote:
> I think the point is for there to be something in the standard library
> or Python core that makes it easy for a consumer to *copy* the data to a
> contiguous memory segment in the event the consumer can't directly
> handle non-contiguous data
It would be even more useful
Josiah Carlson wrote:
> "Travis E. Oliphant" <[EMAIL PROTECTED]> wrote:
>> abstractly as if it were. I believe, the PIL is where the idea of
>> multiple buffer segments in the original buffer interface came
>> from, I believe.
>
> Remove the last "I believe" in that sentence and remove
"Travis E. Oliphant" <[EMAIL PROTECTED]> wrote:
> abstractly as if it were. I believe, the PIL is where the idea of
> multiple buffer segments in the original buffer interface came
> from, I believe.
Remove the last "I believe" in that sentence and remove the commas. ;)
> The buf
Attached is my revised PEP for the buffer protocol after incorporating
suggestions from Greg Ewing. It is as simple as I can make it and
still share what I think needs to be sharable. Suggestions are
welcome. I will provide and maintain code to implement the PEP when
the basic idea of t
