Go 1.17 is deprecating the traditional use of 'go get'

Re:Go 1.17 is deprecating the traditional use of 'go get' by slavik81 on Friday June 25, 2021 @02:07PM (#27634303)

Python 3 IO isn't UTF-8. The entire point of the change was to support _arbitrary_ encodings (most of which are legacy code pages).

Python would sometimes guess the output encoding on Windows to be ASCII even when UTF-8 was supported by the output device. So you'd end up with encoding-oblivious Python 2 programs that worked perfectly reading and writing UTF-8, and Python 3 programs that failed upon encountering a non-ASCII character.

They've since improved the defaults on Windows, but the changes in Python 3 that caused me a lot of pain were when they made IO to be non-Unicode.

[ Parent | on HN ]

Re:Go 1.17 is deprecating the traditional use of 'go get' by kortex on Friday June 25, 2021 @03:10PM (#27635004)

Man, it's it's harrowing in hindsight to look back on porting 2->3 on linux, and remembering my coworkers that had to do it on Windows with encoding-oblivious libraries.

They're still constantly finding bits of code that break cause some customer decided to switch from "delta" to “Δ” in some machine learning log output.

[ Parent | on HN ]