News for hackers. Stuff that matters.
Re:What’s New in Python 3.7 by noselasd on Sunday September 17, 2017 @11:54AM (#15270178)
If it was changed from ascii to utf-8, how does it break everyting else ?
Re:What’s New in Python 3.7 by user5994461 on Sunday September 17, 2017 @03:07PM (#15271158)
ASCII doesn't exist as such.

Characters are encoded in one byte and ascii leaves the highest 128 characters undefined. They are interpreted system-wise, depends on the locale and user settings.

Re:What’s New in Python 3.7 by warbiscuit on Sunday September 17, 2017 @11:02PM (#15273092)
"ascii" the codec does exist under python. It's strictly defined as byte values 0-127, anything in the 128-255 range causes a decoding error...

    >>> b"abc\xf0".decode("ascii")
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xf0 in position 3
Thus, moving the default from "ascii" to an ASCII-superset should have no decoding issues for previously valid files, since those bytes were never valid to start with.
Re:What’s New in Python 3.7 by noselasd on Monday September 18, 2017 @01:29PM (#15277787)
ASCII very much exists - but what you describe is an entierly different thing. Sure - if the change is from default-user-locale to UTF-8, things would break.

But if the changelog is truthful, and the change is from ASCII to UTF-8, things should not break - at least not to any great extent.