Hi @Delgan! I tried to reproduce this issue, but it seems to be working fine here:

# pip3 list | grep colorama
colorama                      0.4.1

# python -i
Python 3.7.4 (default, Jul 11 2019, 09:35:14)
[GCC 9.1.0] on msys
Type "help", "copyright", "credits" or "license" for more information.
>>> from colorama import init
>>> init()
>>> print("\033[31m" "some text" "\033[0m")
some text
>>>

# uname -a
MSYS_NT-10.0-18362 DESKTOP 3.0.7-338.x86_64 2019-07-11 10:58 UTC x86_64 Msys

some text is red.

Hey @1138-4eb. :)

Could this be because I'm using the full "MINGW" emulator, while you are using the minimalist "MSYS"? I'm not sure of why your git-bash.exe and mine are different. 😕

I'd say that both of us are using the same MSYS/MINGW shell (no matter MSYS, MINGW64 or MINGW32). I installed it with http://repo.msys2.org/distrib/x86_64/msys2-x86_64-20190524.exe. However, environments are not exactly the same:

• Your version is 2.11.2 2018-11-10. Mine is 3.0.7 2019-07-11. This is probably because you didn't execute pacman -Syu recently. It should not be relevant, tho.
• I installed Python through pacman. I think you installed it with binaries/tarballs from https://www.python.org/downloads/release/python-374/. That's why mine says on msys and yours on win32.

FTR, I tried the snippet on cmd and powershell. Both of them use Python from C:\msys64\usr\bin, because it is available in the PATH. On both of them colours are properly shown.

Therefore, I think that this might be an issue when Python is installed 'natively'. Did you try with cmd and/or powerhsell?

You are correct, I installed Python using the binaries on python.org. colorama works fine with bash and powershell. As discussed, it only fails when invoked from git-bash.exe which I downloaded as a PortableGit: https://git-scm.com/download/win. I do not have access to the pacman command. 😕

I think you are right, it works fine for you because MINGW64 uses its own Python installation, while in my case it uses the one from Windows.

colorama works fine with bash and powershell.

I wonder where is that bash coming from. Is it an alias provided by powershell? Is it WSL? It can't be git-bash.exe, and you don't have MSYS2 neither.

As discussed, it only fails when invoked from git-bash.exe which I downloaded as a PortableGit: https://git-scm.com/download/win. I do not have access to the pacman command. 😕

You don't have pacman because git-bash.exe is an stripped down distribution which is expected to run git only. See https://stackoverflow.com/questions/25019057/how-are-msys-msys2-and-msysgit-related-to-each-other

If you switch from 'Git for Windows' to MSYS2, you can install pacman -S git and you will feel little to no difference. MSYS2 is quite heavier, tho. My C:\msys64 takes 9GB (I have Python, gcc, etc. installed there).

I think you are right, it works fine for you because MINGW64 uses its own Python installation, while in my case it uses the one from Windows.

I think that the last cases to try are the command prompt and MSYS2 with a non-mingw Python installation. Did you try the former?

Ref VUnit/vunit#539

@1138-4eb Oups, sorry, you wrote "bash" but my brain read "cmd". Of course, I could not and I did not test with bash.

So, I tried to run my Windows Python from MSYS2 and the result was the same, no colors:

@Delgan,

• Does using envvar PYCHARM_HOSTED=1 work for you?
• Did you try support mintty (MSYS/Cygwin terminals) #226?

Refs:

• How to enable colorama in Gitlab tty (and other online services that seem to support colors in terminal) #214
• Added FORCE_COLOR and NO_COLOR environment variables #230
• Color support on Windows: TerminalWriter (PY_COLORS), colorama (PYCHARM_HOSTED) tox-dev/tox#1468

@1138-4eb Both solutions work! I think one may solve this by checking for the "TERM" environment variable in addition to "PYCHARM_HOSTED".

#226 worked for me too!

What did you set the value of the environment variable "TERM" to be?
What is the value of the variable "PYCHARM_HOSTED"?

@jyotsnarupaliya At the time I tried, "PYCHARM_HOSTED" was probably not set as I was testing from the command line. But it can be set to "1" as a workaround to enable colors:

The "TERM" environment variable is not checked by colorama, but it could have been used to detect bash-like tools that support ansi codes on Windows (like git-bash.exe).

I stumbled accross this issue as well, is there a long term solution planned?