Re:Mercurial’s journey to and reflections on Python 3
by Jasper_ on Monday January 13, 2020 @06:50PM
(#22040127)
Right, moving to std::cout to fmt could be as simple as a find-and-replace fix. That the C++ committee could have inflicted this minimal pain on their users, but chose not to do it, shows some amount of concern for backwards compatibility and old codebases. By comparison, Python 3 changed the entire text model and dropped the mic, and waited for 8 years to start to pick the pieces back up.
Re:Mercurial’s journey to and reflections on Python 3
by choppaface on Monday January 13, 2020 @08:37PM
(#22040963)
I guess I don’t understand your argument that “Python 3 changed the entire text model and dropped the mic.” format strings are optional; the old % operator still works fine. The change to unicode is dramatic, but personally I haven’t run into major problems. I’ve had unit tests break because of it, but that’s why one has unit tests. I’ve also worked on a very large python webapp that underwent painful internationalization, and in that case we ended up using unicode strings everywhere anyways.
Re:Mercurial’s journey to and reflections on Python 3
by richardwhiuk on Sunday January 19, 2020 @02:09PM
(#22093236)
The % didn't use to work fine. .iteritems() was made for no good reason.
Python 3 could have required all strings began with u" or b", but they didn't - they did something which encouraged breakage.
The compiler support for C++11 (and especially inconsistencies in Debian packages, compiled flags, etc) was a very painful issue for several years. But auto is that useful ...