RetroSearch Browse

Wed Jan 15 17:18:54 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-January/131642.html

On Wed, 15 Jan 2014, Antoine Pitrou wrote:

> On Wed, 15 Jan 2014 15:47:43 +0000 (UTC)
> Neil Schemenauer <nas at arctrix.com> wrote:
>>
>> Objects that implement __str__ can also implement __bytes__ if they
>> can guarantee that ASCII characters are always returned, no matter
>> what the *value*
>
> I think that's a slippery slope. __bytes__ should mean that the object
> has a well-known bytes equivalent or encoding, not that its __str__
> happens to be pure ASCII.

+1

> (for example, it would be fine for a HTTP message class to define a
> __bytes__ method)
>
> Also, consider that if e.g. float had a __bytes__ method, then
> bytes(2.0) would start returning b'2.0', while bytes(2) would still
> need to return b'\x00\x00'.

Not actually suggesting the following for a number of reasons including
but not limited to the consistency of floating point formats across
different implementations, but it would make more sense for bytes (2.0) to
return the 8-byte IEEE representation than for it to return the ASCII
encoding of the decimal representation of the number.

Isaac Morland			CSCF Web Guru
DC 2619, x36650			WWW Software Specialist

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-January/131642.html below:

[Python-Dev] PEP 461 - Adding % and {} formatting to bytes