←back to thread

PEP 686 – Make UTF-8 mode default

(peps.python.org)
238 points GalaxySnail | 8 comments | 26 Apr 24 11:55 UTC | HN request time: 0.408s | source | bottom
Show context
nerdponx ◴[26 Apr 24 14:44 UTC] No.40169967[source]▶
Default text file encoding being platform-dependent always drove me nuts. This is a welcome change.

I also appreciate that they did not attempt to tackle filesystem encoding here, which is a separate issue that drives me nuts, but separately.

replies(4): >>40171063 #>>40171211 #>>40172228 #>>40173633 #
layer8 ◴[26 Apr 24 16:10 UTC] No.40171063[source]▶
Historically it made sense, when most software was local-only, and text files were expected to be in the local encoding. Not just platform-dependent, but user’s preferred locale-dependent. This is also how the C standard library operates.

For example, on Unix/Linux, using iso-8859-1 was common when using Western-European languages, and in Europe it became common to switch to iso-8859-15 after the Euro was introduced, because it contained the € symbol. UTF-8 only began to work flawlessly in the later aughts. Debian switched to it as the default with the Etch release in 2010.

replies(4): >>40172024 #>>40172052 #>>40172183 #>>40177841 #
Dylan16807 ◴[26 Apr 24 17:35 UTC] No.40172052[source]▶
> Not just platform-dependent, but user’s preferred locale-dependent.

Historically it made sense to be locale-dependent, but even then it was annoying to be platform-dependent.

One is not a subset of the other.

replies(2): >>40172171 #>>40172645 #
1. hermitdev ◴[26 Apr 24 17:45 UTC] No.40172171[source]▶
> platform-dependent.

It's 2024 and we still can't all agree on line endings. Mac vs Win vs Unix...

replies(2): >>40172265 #>>40172368 #
2. Y-bar ◴[26 Apr 24 17:55 UTC] No.40172265[source]▶
Mac OS and Unix agreed about twenty years ago to use the same ending: https://superuser.com/a/439443
replies(1): >>40172390 #
3. Longhanks ◴[26 Apr 24 18:05 UTC] No.40172368[source]▶
It's 2024, everything but Windows is UTF-8 \n since twenty years.
replies(1): >>40174531 #
4. Dylan16807 ◴[26 Apr 24 18:08 UTC] No.40172390[source]▶
By which time XP was already in the middle of releasing, so it was too late to get Windows on board.

It's too bad, with a bit more planning and an earlier realization that Unicode cannot in fact fit into 16 bits then Windows might have used UTF-8 internally.

replies(2): >>40174470 #>>40196503 #
5. jmb99 ◴[26 Apr 24 21:23 UTC] No.40174470{3}[source]▶
Unless I’m mistaken, Rhapsody (released 1997) used LF, not CR. At that point it was pretty clear Mac was moving towards Unix through NeXTSTEP, meaning every OS except windows would be using LF. Microsoft would’ve had around 6 years before the release of XP, and probably would’ve had time to start the transition with Win2K at the end of 1999.
replies(1): >>40177690 #
6. int_19h ◴[26 Apr 24 21:29 UTC] No.40174531[source]▶
Linux was definitely not uniformly UTF-8 twenty years ago. It was one of the many available locales, but it was still common to use other encodings, and plenty of software didn't handle multibyte well in general.
7. mixmastamyk ◴[27 Apr 24 06:11 UTC] No.40177690{4}[source]▶
Every OS except the one that had 95% market share in late 90s. Apple was only propped up “Weekend at Bernies” style to appease regulators.
8. account42 ◴[29 Apr 24 10:11 UTC] No.40196503{3}[source]▶
> and an earlier realization that Unicode cannot in fact fit into 16 bits

The Unicode consortium already realized it when they decided on Han unification, they just didn't accept it yet.