OSError: [WinError 6] The handle is invalid with pytest or tox

When running in pytest or tox got this error

def alive_repr(spin=''):
        update_data()

        line = '{} {}{}{} in {} {} {}'.format(
            bar_repr(run.percent, end), spin, spin and ' ' or '',
            monitor(), to_elapsed(), run.stats(), run.text or title or ''
        )

        line_len = len(line)
        with print_lock:
            if line_len < run.last_line_len:
                clear_traces()
>           sys.__stdout__.write(line + (spin and '\r' or '\n'))
E           OSError: [WinError 6] Das Handle ist ungültig

but progress bar is done

here with tox:

test code:

from alive_progress import alive_bar


def test_progress():
    items = range(1000)                  # retrieve your set of items
    with alive_bar(len(items)) as bar:   # declare your expected total
        for item in items:               # iterate as usual
            # process each item
            bar()                        # call after consuming one item


if __name__ == "__main__":
    test_progress()

tox

[tox]
skip_missing_interpreters = True
ignore_basepython_conflict = true
envlist =
    py{36, 37, 38},

[testenv]
setenv =
    PYTHONUNBUFFERED=yes
skip_install = true
deps =
    pytest
    alive-progress
commands =
    pytest {posargs}

calling it directly make no problems

[rsalmei]

Yeah man, unfortunately it is…

Well, I’ve found this answer that could help: https://stackoverflow.com/a/27093194

Also this readme explains a lot: https://github.com/Drekin/win-unicode-console See: The standard stream objects (sys.stdin, sys.stdout, sys.stderr) are not capable of reading and displaying Unicode characters in Windows console.

Anyway, do you really need WindowsOS support? Actually I didn’t even know alive-progress didn’t work on it, as no one had ever complained about it. So it would be pretty low on my priority to try to support it…

[rsalmei]

Hey, I just found out that Windows Terminal does support Unicode. give it a try!

I’ve installed Python on a Windows machine, and ended up stuck with another bug: #50 I’ll close this one for now, feel free to reopen if you have any more information.