I agree with a lot of what you're saying. On Django though (or any library that intends to drop 2.x support), I feel if they truly go through with it, they'll b

I agree with a lot of what you're saying. On Django though (or any library that intends to drop 2.x support), I feel if they truly go through with it, they'll be in for a shock. It will more than likely hurt them more than it hurts Python2 (I also don't understand the obsession with people wanting to kill or hurt Python2). People and companies may be more likely to start new projects in Flask or another alternative, maybe even fork Django which would be a disaster for them. But as of today, Django's roadmap has the LTS release that supports 2.x as an unknown EOL. So it won't be anytime soon. Overall I tend to agree that Python3 will eventually take over. That wasn't what I was arguing and I never said otherwise in my posts. My problem is with the harassment over Python2 folks to port and all the associated nonsense. That's the part that is more counterproductive than anything. "A matter of time" is a really bad last leg to stand on as well, because time has an awfully broad range. :) As far as the other points, I have doubts about the impact of Ubuntu or others defaulting to Python3. That won't stop me from building for PyPy, I can say that at least. In general I feel that I'm on a similar page to your stance though. I do use Python3, and have since the 3.0 release in testing alone. For someone who has tried every release and found performance issues and bugs galore, it's a testament that I (and others) haven't given up completely. I think many have.