It's hard to remember now but the problem wasn't so much any changes to the language. It was that the C-api changed. Since most of the important libraries have

It's hard to remember now but the problem wasn't so much any changes to the language. It was that the C-api changed. Since most of the important libraries have C-components, this meant that it took a long time for the libraries to become available on python3. Now, many of the libraries have shifted so we're on to the next problem which is that many companies have legacy code bases or very conservative update cycles which is keeping people stuck on python2 (both are the case for me). Of course, there will always be those who find problems with any change and they're normally the most vocal. Personally, I've struggled with various unicode issues in my code over the last few years and python3 might have saved me from all that. Even so, for a long time python3 didn't seem to offer enough of an advantage to make the switch although I have ported some of my code across which was relatively easy. The hardest thing for me is that python3 has banned implicit relative imports within packages. Unfortunately I've tended to mix modules and scripts freely in my projects (scientific simulations) and so I'll need to restructure to port some of my projects.