-
-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConsoleZ does not show report colors #2337
Comments
This problem is not limited to Windows and its caused by loss of |
@margars please post the project you're using to replicate this and the terminal (with version) you're running in. |
Initially I observed the issue with ConsoleZ, but later I tried using Windows default PowerShell and CMD, in all cases the output is not displayed correctly. My project is restricted by company policies, cannot post it. |
I marked this one hard, because doing true pty emulation on Windows is not a well trod path. However, it might be possible to use the tox3 behavior of not passing file handles to subprocess stdout/stderr. Normally, this would break command logging, but maybe instead some windows-specific API might be used to read/spy the child process console streams, so they wouldn't have to be redirected at the subprocess layer. This kind of implementation could be simpler than pty if logging output is the only reason to have pty emulation. |
When tox4 is executed from PowerShell (5) on Windows (10), the color output from mypy/pytest is not displayed correctly. The same issue is also observed when using CMD. On the same environment running tox 3 produces output as expected.
Here is an example (tox4):
tox3 example:
The final message is displayed correctly (tox4):
The text was updated successfully, but these errors were encountered: