Remove support for windows #46 - Gibberish stdout in windows

[kman0]

Remove support for windows #46

[msabramo]

@sontek, @Frozenball: Did you guys ever run pytest-sugar on Windows?

I imagine it works in Cygwin with little to no work?

[Teemu]

I have never tried it on Windows, only on Mac/Linux enviroments.
On 5 Dec 2014 19:57, "Marc Abramowitz" [email protected] wrote:

@sontek https://github.com/sontek, @Frozenball
https://github.com/Frozenball: Did you guys ever run pytest-sugar on
Windows?

I imagine it works in Cygwin with little to no work?

—
Reply to this email directly or view it on GitHub
#49 (comment)
.

[Dog]

I am currently running this in Windows 7 under GitBash with ConEmu. It is not displaying for me properly, and I also get gibberish from stdout. I can debug further if there is something else you'd like me to try.

[wwwald]

The gibberish appears because the Windows console used codepage 850 by default (MS-DOS Latin 1). Changing this to codepage 65001 = UTF-8 fixes the gibberish.

chcp 65001

Mind you: the actual characters that appear also depend on the console font that is used, and the console environment. With font Lucida console and the alternative "cmder" console, I see pretty decent py.test output:

[Natim]

Then we should probably add this in the troubleshooting part of the documentation.

[Teemu]

Let's add this to documentation

[cb109]

Just to elaborate on this for other Windows users: I am using the git bash on Windows together with ConEmu and had struggles to make this work.

Setting the codepage in a git bash will only work with a small change:
$ chcp.com 65001

This however will be recognized as cp65001 by python instead of the correct 65001 (at least on 2.7x), it seems to be a bug. We can map that to the correct codec though. Inside my top-level conftest.py I was able to produce decent output with the following adjustments:

Don't forget to first: $ pip install colorama

import codecs
codecs.register(lambda name: codecs.lookup('utf-8') 
                if name == 'cp65001' else None)

import colorama
colorama.init()

Some special characters still seem to not be recognized, but at least the progress bars look ok.

[max-sixty]

FYI I have this problem when running tests inside a docker container. Container is running ubuntu 16, local is macOS.

[Teemu]

Are we sure it's pytest-sugar issue and not a problem in Docker etc.?

[max-sixty]

Thanks for responding @Frozenball

It's definitely coincident with pytest-sugar - it was fine before, the gibberish when pytest-sugar was installed, then fine when reverted...

But it might be because Docker can't display complex stdout, or something else that's unavoidable. I'm less familiar with the mechanics there

[anntzer]

For slightly better Windows support, you may want to consider switching the dependency from termcolor to colorama, which should provide the same features, but, as mentioned in #49 (comment), can additionally preprocess ANSI color codes on Windows (see e.g. Description at https://pypi.org/project/colorama/).