There were valid reasons to be upset at Python 3's handling of Unicode. - https://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ https://lucumr.pocoo.org

There were valid reasons to be upset at Python 3's handling of Unicode. - https://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ https://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ - Discussion: https://news.ycombinator.com/item?id=7732572 https://news.ycombinator.com/item?id=7732572 - https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journey-to-and-reflections-on-python-3/ https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journ... - Discussion: https://news.ycombinator.com/item?id=22036773 https://news.ycombinator.com/item?id=22036773 Chalking these complaints up to bad development practices is _precisely_ the reason why the Python 3 migration was handled so poorly. If this attitude is repeated for no-GIL Python, it will fail.