Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
A summary of the comment thread with jmathew: The simplest workaround is to use winpty, i.e. write: $ winpty black version.py The reason this works is that the Python build that I am using and...
Answer
#1: Initial revision
by
boudewijn21
·
2022-04-21T09:33:51Z (about 2 years ago)
A summary of the comment thread with jmathew: The simplest workaround is to use winpty, i.e. write: ```bash $ winpty black version.py ``` The reason this works is that the Python build that I am using and the Python console scripts are expecting a Windows terminal, but Git Bash is not one. Winpty fixes this. See also: https://stackoverflow.com/questions/32597209/python-not-working-in-the-command-line-of-git-bash/36530750#36530750 This can be simplified by adding aliases to your `.bashrc` file: ```bash alias black='winpty black' ``` which will allow you to again type: ```bash $ black version.py ``` Something I did not investigate is building Python without ncurses support: https://stackoverflow.com/a/32599341/2505165 Moving away from Git Bash, solutions are to use WSL or Cygwin.