&gt; I wouldn&#x27;t build any project in Python3 today, because the prod-ready PyPy option isn&#x27;t there which adds CPU performance as a Python feature and removes the GIL.<p>But... that&#x27;s a corner area of Python. Not everyone needs GIL-less STM, and arguably if you&#x27;re using tonnes of threads maybe you&#x27;re doing it wrong? Perhaps you should try asyncio :)<p>I mean that reason doesn&#x27;t even make sense - I&#x27;m not using PyPy3 because of the GIL. Great, so uhh what about Django apps? What about small scripts and projects? What about using it for anything other than highly threaded applications that benefit from no GIL?<p>&gt; Just because you agree with part of my post and arguments doesn&#x27;t mean you have to downvote<p>I didn&#x27;t (and I wouldn&#x27;t have), I just upvoted after reading &quot;This being another attempt to make Python2 look as old and crufty as possible&quot; - thinking you viewed this in a positive light.<p>&gt; frankly find the vocal Python3 promoters to be the loudest of the bunch<p>I see the opposite. I see lots of people angry about a statement being turned into a function, angry at not understanding encoding and angry at the Python developers. People demanding a JIT in cPython, people crying about type annotations, etc. Plus a shedload of FUD.<p>I&#x27;m sorry, your comments reek of someone angry for not very good reasons and I can&#x27;t work out why. Python 3 is a much much nicer language to work with, it&#x27;s more consistent and has less WTF&#x27;s (along with far less UnicodeEncodeErrors). I took the plunge a year ago and won&#x27;t ever look back, coding in 2.7-8 at work hurts.<p>I know Mark Lutz is well respected but that doesn&#x27;t make some of his comments on Python 3 less silly. Anything that has been added to Python 3 has a comment explaining why it sucks, and most of those explanations are senseless. Even things like the statistics module - apparently that sucks because NumPy is better? He implies that should be bundled instead. :&#x2F;<p>The matrix operator saves 3+ lines of Numpy code (and is a common operation). This of course sucks because &quot;it&#x27;s not used by the core language&quot;. Oh and it &quot;expands Python&#x27;s complexity and learning curve needlessly&quot;, despite not being used by the core language. Ok Mark.