-
-
Notifications
You must be signed in to change notification settings - Fork 533
Tox raises an exception when parsing logs containing the 0x85 character (…) #1506
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
Comments
I can't reproduce, the line in that stacktrace doesn't exist at the latest version: Line 107 in 1b8f302
(notice yours says I suspect you've corrupted your installation of |
Mmm, true, I can't even reproduce it; |
Oh actually, I broke the tox installation while debugging it, but there was indeed a problem, the stacktrace I initially wrote was wrong. With the repro repo, you should see the error using the parallel flag :
|
I still can't reproduce, though I suspect it's because you're on windows (and perhaps have locale misconfigured?) -- can you try setting the root cause is the underlying thing (I believe in this case pipenv?) is printing cp1252 code points: >>> b'\x85'.decode('cp1252')
'…' it should be producing the UTF-8 sequence ( |
I've tried setting my locale; both outside and within tox, but pipenv keeps printing 0x85 instead of its utf-8 equivalent... I can confirm that this is definitely a Windows problem; I can't reproduce it on either Linux nor Mac. It might be a |
hmm that is an interesting point, didn't realize this was different parallel vs not -- I guess if we're handling this properly serially we should fix parallel -- thanks for the issue and we can dig into the root cause 👍 |
Dear Tox maintainers,
We are using Tox with pipenv, and it currently raises an exception when pipenv writes the
…
character in the logs. (which is pretty much everywhere). Tox successfully executes though, so for us it is mainly an aesthetic problem, but it might hide other issues.Sounds like an encoding problem.
Here is a repro repo : https://github.com/franknarf8/tox-issue-repro
(I am encountering this behavior on Windows 10)
here is the output of
tox -rvv
:Have fun debugging this and thank you for maintaining this awesome tool!
The text was updated successfully, but these errors were encountered: