Only if you didn't know that b'' is an alternative to bytes(). The b''
notation is so much more compact and so much more helpful that I
really don't want to go back to it. We will somehow have to deal with
this through education and documentation.
http://bugs.python.org/issue3220
Improve Bytes
Hi,
I've submitted a final patch with the following variations:
- no additions or changes to public APIs
- tracebacks are standardized as suggested by Georg Brandl
- reference cycles along the __context__ chain are broken in PyErr_SetObject
(it is an O(n) linear search but should show almost z
2008/6/27 Guido van Rossum <[EMAIL PROTECTED]>:
> Only if you didn't know that b'' is an alternative to bytes(). The b''
> notation is so much more compact and so much more helpful that I
> really don't want to go back to it. We will somehow have to deal with
> this through education and document
On Fri, Jun 27, 2008 at 5:16 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> 2008/6/26 Georg Brandl <[EMAIL PROTECTED]>:
>
>> Yes. Bytes objects are sequences of bytes, which are integers.
>> So, in short, this is the way they work.
>
> I think that the OP confusion comes from the representation.
2008/6/26 Georg Brandl <[EMAIL PROTECTED]>:
> Yes. Bytes objects are sequences of bytes, which are integers.
> So, in short, this is the way they work.
I think that the OP confusion comes from the representation.
We have a data type called bytes. They are sequences of bytes. So, I build one:
>>
