[Python-3000] Thoughts on new I/O library and bytecode

[Neil Schemenauer]

Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> That's my point -- you *don't* know how any given bytes
> object was created, so there's no reason to display it
> in anything other than the most generic way.

Practicality beats purity here, I think.  For example, if I'm
debugging a network protocol, I'd prefer

    b"EHLO ...\x0d\x0a"

over 

   bytes([69, 72, 76, 79, ..., 13, 10])

Cheers,

  Neil