New submission from Mark Summerfield [EMAIL PROTECTED]:
I know it is almost certainly too late, but I think a lot of people will
be confused by str.decode() and bytes.encode() (or was that the other
way around)?
Calling the methods str.tobytes() and bytes.tostr() (or nicer,
str.to_bytes() and
Benjamin Peterson [EMAIL PROTECTED] added the comment:
-1
encoding and decoding is generally accepted terminology. Besides then we
would be binding ourselves to returning bytes or a str; that's not
necessarily guaranteed.
Anyway, I think this hardly has a chance in the place we are (between
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
There's nothing new to .encode() and .decode(). They have existed since
Python 1.6.
--
nosy: +lemburg
resolution: - wont fix
status: open - closed
___
Python tracker [EMAIL PROTECTED]