[issue3252] str.tobytes() and bytes/bytearray.tostr()

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]>

[issue3252] str.tobytes() and bytes/bytearray.tostr()

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > encoding and decoding is generally accepted terminology Yes, but I personally always pause a couple of seconds each time I have to write "encode" or "decode". Following Mark's idea, I think I will mentally use "en-bytes" and "de-bytes

[issue3252] str.tobytes() and bytes/bytearray.tostr()

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 be

[issue3252] str.tobytes() and bytes/bytearray.tostr()

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