Steve Dower added the comment:
> IIRC, ANSI is somewhat incompatible with sending random binary gibberish to
> the screen, as people accidentally do with TYPE sometimes :) But the random
> binary gibberish may contain ANSI control sequences... That's why I'm
> negative on making it a default.
I don't actually know how big a deal this would be. I seem to get identical
results from "print(''.join(chr(x) for x in range(32)))" both with and without
the VT100 flag set, though of course "print('\033[91m')" behaves differently.
But given "on by default" isn't popular, and "off by default" implies adding
new public API that is already available either as a short ctypes snippet or a
number of 3rd-party libraries, I think we should consider this rejected.
For future reference, the python-ideas thread starts with
https://mail.python.org/pipermail/python-ideas/2016-December/044033.html
----------
resolution: -> rejected
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29059>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
