I didn't miss it, and I don't disagree, I just don't think it has much bearing on the discussion (which is whether to go with this proposal at all).
On 9/27/07, Talin <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > Thinking through the consequences, and noticing that using the array > > module as an ersatz mutable bytes type is far from ideal, and > > recalling a proposal put forward earlier by Talin, I floated the > > suggestion to have both a mutable and an immutable bytes type. (This > > had been brought up before, but until seeing the evidence of Jeffrey's > > patch I wasn't open to the suggestion.) > > One thing that you may have missed from my proposal is that both 'bytes' > and 'buffer' inherit from a common ABC. This ABC defines all of the > operations which 'bytes' and 'buffer' have in common. My name for this > ABC was 'ByteSequence', but I have no particular attachment to that name. > > -- Talin > > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
