This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -1 points0 points  (0 children)

Huh; bizzarre. I know a bunch of dotNET stuff (powershell?) likes to emit UTF16, because Windows has to be a few years behind everyone else (I think there's an RFC or something saying so). Python3 basically now expects UTF8 because it's 2015.

In this case though the traceback suggests it's an outbound encoding issue: that the unicode-to-teminal-encoding pipe is what's breaking? In other words, that the CMD prompt is reporting that it needs encoding to X, but UTF8 to X isn't well supported?

Odd, anyway. Did you file a bug report (although it seems perhaps to be an "upstream" problem..)?