Skip to content
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

Windows breakage when defaultencoding for non-unicode applications is ... #576

Closed
bunnyevans opened this issue Apr 7, 2020 · 2 comments
Closed

Comments

@bunnyevans
Copy link

W10 with default encoding for non-unicode programs = Japanese
(cp932)

Attempt to create a project with esp-idf

= boom.

bang1.txt

This appears to be because python is picking up the system encoding, going "oh, I'm JAPANESE" and then falling flat on its face. So much for unicode...

As a non-python-programmer I am unable to fix this short of having a completely separate windows machine that is entirely in English.

@valeros
Copy link
Member

valeros commented Apr 7, 2020

Hi @bunnyevans ! Thanks for the report. Looks like, there is a problem in internal ESP-IDF tools and will be resolved in the next release. Please take a look a this issue espressif/esp-idf#4977

@valeros valeros closed this as completed Apr 7, 2020
@bunnyevans
Copy link
Author

Fascinating, but ideally it should be starting python with whatever magical flags it needs to ignore systemlocale (cp932 et cetera) and running it in unicode.

Possibly like: https://docs.python.org/3/using/windows.html
Section 3.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants