You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent upgrade to the Windows 10 console resulted in VT mode being disabled by default for child processes. This breaks the ansi escape codes being converted into color.
Microsoft's turn-off of ANSI coloring is definitely a bummer for colored text.
It's still an open question whether it's the responsibility of an ANSI-text generation library to try to fix it. I understand why it'd be convenient, and why it's annoying ANSI isn't enabled automatically. But twiddling Win32 control bits? That's a very specific and invasive side-effect—one that seems outside ansicolor's remit. Related: It's a side-effect that'd be hard-to-impossible for us to reliably test.
A recent upgrade to the Windows 10 console resulted in VT mode being disabled by default for child processes. This breaks the ansi escape codes being converted into color.
This answer on StackOverflow fixes it:
http://stackoverflow.com/a/36760881/272238
Here is an explanation of the change that was introduced: microsoft/WSL#1173 (comment)
And here are Python devs refusing to do anything about it in the python interpreter:
https://bugs.python.org/issue29059
So for this module it'd be great to add:
when the platform is on windows.
The text was updated successfully, but these errors were encountered: