[Python-Dev] Inconsistent Use of Buffer Interface in stringobject.c (original) (raw)

Phil Thompson phil at riverbankcomputing.co.uk
Mon Oct 24 20:56:26 CEST 2005

On Monday 24 October 2005 7:39 pm, Guido van Rossum wrote:

On 10/24/05, M.-A. Lemburg <mal at egenix.com> wrote: > Guido van Rossum wrote: > > A concern I'd have with fixing this is that Unicode objects also > > support the buffer API. In any situation where either str or unicode > > is accepted I'd be reluctant to guess whether a buffer object was > > meant to be str-like or Unicode-like. I think this covers all the > > cases you mention here. > > This situation is a little better than that: the buffer > interface has a slot called getcharbuffer which is what > the string methods use in case they find that a string > argument is not of type str or unicode.

I stand corrected! > As first step, I'd suggest to implement the gatcharbuffer > slot. That will already go a long way. Phil, if anything still doesn't work after doing what Marc-Andre says, those would be good candidates for fixes!

I have implemented getcharbuffer - I was highlighting those methods where the getcharbuffer implementation was ignored.

I'll put a patch together.

Phil

More information about the Python-Dev mailing list