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
Hi. I have been using colorama since quite a while, and I see it automatically disable itself when executed outside of a terminal, to avoid unwanted ascii string everywhere on the screen.
But since some CI such as Gitlab or Travis does support colors in their output, I wonder how colorama would be made compatible, and so identify "hum, this is not a tty on a terminal that support colors, but i recognise such or such environment and so I keep the color on". Maybe by a environment variable?
The text was updated successfully, but these errors were encountered:
There's also the method of using "strip=True, convert=True" directly with the AnsiToWin32 object.
I agree however that COLORAMA_FORCE_COLOR and possibly FORCE_COLOR as a fallback should be honored (instead of only "PYCHARM_HOSTED").
I've tested / looked into this for Windows builds on Travis.
With regard to that it looks like the "winterm" check (to setup the dict of conversions) is not True already likely (
Hi. I have been using colorama since quite a while, and I see it automatically disable itself when executed outside of a terminal, to avoid unwanted ascii string everywhere on the screen.
But since some CI such as Gitlab or Travis does support colors in their output, I wonder how colorama would be made compatible, and so identify "hum, this is not a tty on a terminal that support colors, but i recognise such or such environment and so I keep the color on". Maybe by a environment variable?
The text was updated successfully, but these errors were encountered: