This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients serhiy.storchaka, taleinat, terry.reedy
Date 2020-06-28.20:29:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593376150.13.0.678353080041.issue41148@roundup.psfhosted.org>
In-reply-to
Content
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 locale.getpreferredencoding().  For me, this is cp1252.  (Changing the console codepage with chcp or the process locale with setlocale don't change this.  Something else might.)  So this issue currently has nothing to do with iomenu.encoding.  Rather it is a proposal that IDLE explicitly pass a locale, in particular 'utf-8'.  This has the same issues given above.
History
Date User Action Args
2020-06-28 20:29:10terry.reedysetrecipients: + terry.reedy, taleinat, serhiy.storchaka
2020-06-28 20:29:10terry.reedysetmessageid: <1593376150.13.0.678353080041.issue41148@roundup.psfhosted.org>
2020-06-28 20:29:10terry.reedylinkissue41148 messages
2020-06-28 20:29:10terry.reedycreate