Message 389083 - Python tracker

➜

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	lemburg
Recipients	eryksun, lemburg, methane, vstinner
Date	2021-03-19.12:48:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<c4d2a975-ef52-8405-8e84-292cdb658aef@egenix.com>
In-reply-to	<1616156703.05.0.889922202114.issue43552@roundup.psfhosted.org>

Content
On 19.03.2021 13:25, Eryk Sun wrote: >> My assumption is that nl_langinfo(CODESET) does not work on Windows >> or gives wrong results. Is that incorrect ? > > There is no such function for CRT locales. I provided two alternatives that would allow implementing this consistent with POSIX, and thus avoid all of the "except on Windows..." disclaimers that have to explain (apologize) that only the process ANSI code page is used in Windows, and, for no good reason as far as I can tell, the LC_CTYPE locale encoding is completely ignored. Sounds good. If we can get consistent behavior on Windows as well, all the better :-)

On 19.03.2021 13:25, Eryk Sun wrote:
>> My assumption is that nl_langinfo(CODESET) does not work on Windows
>> or gives wrong results. Is that incorrect ?
> 
> There is no such function for CRT locales. I provided two alternatives that would allow implementing this consistent with POSIX, and thus avoid all of the "except on Windows..." disclaimers that have to explain (apologize) that only the process ANSI code page is used in Windows, and, for no good reason as far as I can tell, the LC_CTYPE locale encoding is completely ignored.

Sounds good. If we can get consistent behavior on Windows as well,
all the better :-)

History
Date	User	Action	Args
2021-03-19 12:48:02	lemburg	set	recipients: + lemburg, vstinner, methane, eryksun
2021-03-19 12:48:02	lemburg	link	issue43552 messages
2021-03-19 12:48:02	lemburg	create