Terry J. Reedy added the comment:
After writing the above, I discovered that IDLE *itself* does not use any
particular encoding for config files. Its configparser.Configparser subclasses
load function calls .read(filename), which in turn calls open(filename,
encoding=None), which calls
Terry J. Reedy added the comment:
I opened # 41152 to revise the iomenu code setting encoding and errors. The
encoding is always 'utf-8' when testing and running on Windows and, I believe,
macOS. So that and this issues are about finding and using locale on *nix, and
would require testing
New submission from Serhiy Storchaka :
IDLE uses the locale encoding for reading and writing config files. Default
config files are ASCII-only, but if user config files contain non-ASCII data,
it makes them non-portable and depending on the environment of IDLE.
Could they contain file paths?
