Guido van Rossum wrote:
>>In py3k, when the str object is eliminated, then what do you have?
>>Perhaps
>>- bytes("\x80"), you get an error, encoding is required. There is no
>>such thing as "default encoding" anymore, as there's no str object.
>>- bytes("\x80", encoding="latin-1"), you get a bytestring with a
>>single byte of value 0x80.
>
>
> Yes to both again.
Please reconsider, and don't give bytes() an encoding= argument.
It doesn't need one. In Python 3, people should write
"\x80".encode("latin-1")
if they absolutely want to, although they better write
bytes([0x80])
Now, the first form isn't valid in 2.5, but
bytes(u"\x80".encode("latin-1"))
could work in all versions.
Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
