Aren't there too many different Windows installers already? I worry that
it's too hard to choose which one to use (I know I had to ask another
expert :-).
On Mon, Jan 25, 2021 at 7:05 PM Inada Naoki
Sorry for posting multiple threads so quickly.
Microsoft provides UTF-8 code page for process. It can be enabled by manifest file.
https://docs.microsoft.com/ja-jp/windows/uwp/design/globalizing/use-utf8-cod...
How about providing Python binaris both of "UTF-8 version" and "ANSI version"? This idea can provide a more smooth transition of the default encoding.
1. Provide UTF-8 version since Python 3.10 2. (Some years later) Recommend UTF-8 version 3. (Some years later) Provide only UTF-8 version 4. (Some years later, maybe) Change the default encoding
The upsides of this idea are:
* We don't need to emit a warning for `open(filename)`. * We can see the download stats.
Especially, the last point is a huge advantage compared to current UTF-8 mode (e.g. PYTHONUTF8=1). We can know how many users need legacy behavior in new Python versions. That is a very important information for us.
Of course, there are some downsides:
* Windows team needs to maintain more versions. * More divisions for "Python on Windows" environment.
Regards, -- Inada Naoki
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-leave@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/KMYPF7... Code of Conduct: http://python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-c...