> It was truly bizarre that a new, backwards-incompatible version was created really just to fix a missing unicode datatype and add async. That's a very reduct

> It was truly bizarre that a new, backwards-incompatible version was created really just to fix a missing unicode datatype and add async. That's a very reductive way of looking at what was in reality a far more complicated situation, that required a tremendous amount of engineering to even arrive at the compromises they came to. It's not very charitable to all the folks who worked very hard to make that transition even happen. You think they would have actually gone through all this pain and trouble to add a unicode type and some async? You'd think if it were that easy, MS, Google, Dropbox, and friends would have just banded together, slapped on some unicode classes, and called py2.8 a day. The problems necessitating python3 run far deeper than that.