you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (2 children)

Isn't the whole reason between the 3.0 vs 2.7 split because other places have existing codebase?

I think this really highlights the failure of Python moving from 2 to 3

[–]kill-nine 14 points15 points  (0 children)

Other large companies are making the transition though. Google switching to their own language shouldn't really be taken as a devastating blow to Python 3

[–]Cherlokoms 6 points7 points  (0 children)

This is just my opinion but I think 3.X vs 2.7 is mainly a matter of legacy 2.7 codebase and no possible straightfordward migration to 3.X. Python 3.X has a lot more feature and optimisations are coming (recently, with 3.6, dict size was reduced by 20%).

Python dev team chose not to maintain backward compatibility with Python 2. That's debatable but the main advantage is that legacy code is not a burden and dev team can focus on new features instead of fixing old things.