> Serious answer (seriously): because Python 3 didn't break enough stuff. I could also be because there was another choice (which is what you also said). Ruby

> Serious answer (seriously): because Python 3 didn't break enough stuff. I could also be because there was another choice (which is what you also said). Ruby 1.8 -> 1.9 was annoying, but you weren't going to keep using 1.8 given e.g. the speed improvements of 1.9. (Also, who adds breaking changes in minor version numbers?) There's a great talk about changing the culture around Python3 at Facebook[0], I highly recommend it. Technically, it isn't so hard. Culturally, it can be pretty hard. Calling Python2 "Legacy Python" helped at my $work. My boss agreed that continuing 2.x development wasn't a good investment for the future, given the minor technical challanges involved with moving over a few years. [0] https://www.youtube.com/watch?v=nRtp9NgtXiA https://www.youtube.com/watch?v=nRtp9NgtXiA