Open mtribiere opened 4 months ago
That's unfortunate, I know. But sadly, I don't know what to do to circumvent these weird windows incompatibilities...
I'd say perhaps you could try WSL2. Since it is a linux environment it should work flawlessly.
If everything else fails, I think you'd have to use both the classic
bar and spinner, since they only use ASCII characters.
hi ! i do not have a working windows python env to test this but i faced a similar issue while web scraping a while back and adding a bunch of encoding="utf-8"
helped me a lot
you could try to git clone ... && cd ... && pip install -e .
then modify each open(..., mode=...)
in this file alive_progress/tools/unicode_breaks.py
with
with open(..., mode=..., encoding="utf-8") as ...:
...
if this does not fix anything then i would definitely recommand quitting python on windows /s
i also should mention any king of standalone binary made with the alive-progress dependency (pyinstall-ing your code base for example) would need additionnal care since some configuration file are not automatically imported or packed
JIT compiling could in some way produce a similar issue, i'm not an expert though these are suppositions
Thanks @ThomasByr, but I think the unicode "breaks" tool has nothing to do with it since it is not used on the alive_bar
impl at all.
I use this library in a project, and use the CMake/Ninja combo to unittest it. On Linux no issues, but on Windows I have a crash. Probalby some issues with the Powershell encoding. Thanks for your help.
Environment:
CMake/Ninja combo
Log: