4 ms·
+1 Just because we learned to work around unicode issues doesn't mean they're not completely bonkers in 2.7
by kajecounterhack 9y ago
+1
Just because we learned to work around unicode issues doesn't mean they're not completely bonkers in 2.7
- vetinari 9y agoMost people didn't learn to work around unicode issues during the 2.7 time frame. Many third party modules tended to explode spectacularly with encode/decode errors, when they were fed non-ascii strings, when used by people who write using all these funny characters. Just the correct handling of strings in Python 3 alone is a hell of a reason to switch to it.
- bonesss 9y agoLet's not forget the joy of third party libraries that wouldn't fail, but rather silently convert, your data because they had hidden ascii asumptions...