Python 3 making that change is not evidence that enterprise environments do so. Python 2.7 was released over three years ago, and my workplace is still using Python 2.6.6, released about two years ago. Even though Python 2.7 has nice extra features and maintains backwards compatibility with 2.7, they haven't upgraded. And they might upgrade to 2.7 at some point, but if they upgrade to Python 3, just about all existing code breaks, and has to be re-written. If good unit tests weren't written, that's a huge deal. Python not being static means that debugging typically requires running the code, and if you don't get 100% line coverage by your tests, you could have a surprise crash in production.
Companies will happily re-write code if it's worth it. Few seem to have thought Python 3 is worth it. Starting from Python 3? Sure! Upgrading, and breaking existing code? Not as much. Python 3 is great, but it's really just a cleaned up version of Python 2. Many of its nice features have been backported to Python 2.7 (which is what I personally use).
I don't mean to crap on Python 3 at all, it's just that in the business world life isn't as nice as "always use the newest version".
Due to the reasons discussed here
we will be moving to python-forum.io
on October 1, 2016.
This forum will be locked down and no one will be able to post/edit/create threads, etc. here from thereafter. Please create an account at the new site to continue discussion.