Python 3 Is Winning Library Developer Support
It will have taken 8 years for Python3 supporting <i></i>uploads<i></i> to have outpaced Python2. If that&#x27;s not lack of enthusiasm, I don&#x27;t know what is. This is really a pitiful display.<p>It&#x27;s not a surprise though. This all stems back to the original reasons why Python3 was a bad idea. Some things to keep in mind regarding Python2&#x2F;3.<p>- Python3 is pure technical churn, nothing there is true technical innovation. They simply mixed the pot to their liking. Unicode is supported in Python2.<p>- It is slower than Python2 for most people. Though there are crafty arguments out there that it&#x27;s a wash. It&#x27;s really not.<p>- CPython3 was adopted to benefit the core development team, to make it easier to maintain. Not the community on the whole. The community has paid the price by doing a lot of unnecessary ports.<p>- CPython3 was deliberately created to not support Python2 code even though modern VMs can easily support this. The CLR is a great example. They did it this way for their good, not for the community.<p>- In most things in life, you&#x27;d always want to be using the latest supported version. That isn&#x27;t the case here. It may still effectively &quot;fail&quot; with a permanent split. This migration is not even close to being completely in the books and won&#x27;t be for another 10 to 20 years. So why punish yourself moving before it&#x27;s in your best interests. The syntactic differences are so slight, it&#x27;s extremely easy to switch to Python3 if it ever truly reaches Python&#x27;s momentum (this article does not convey momentum holistically, that includes package downloads and the majority of employers using 3).<p>- Related to the bullet above, almost all job opportunities are still Python2.<p>- The ecosystem can&#x27;t keep up, PyPy is still only production-ready on Python2. Python 3.2 support is essentially experimental by comparison.<p>- Many changes and additions are being made and they aren&#x27;t being vetted by the larger community. No significant userbase for Python3 has created this situation. Mistakes are being made and no one is around to speak up because the core devs don&#x27;t care.<p>- Python3 is feature-soup. There is now a new 4th and possibly 5th string formatting method in 3.6 incoming. Really jumped the shark on that one. See Mark Lutz&#x27;s great insight on this topic and more.[0]<p>- Downloads are still dramatically in Python2&#x27;s favor, to this day. Judging from downloads, there&#x27;s a ~10% community userate of Python3.<p>- The bullet above means that the Python3 packages you do use are far less vetted and tested than the Python2 equivalent.<p>- CPython3 was slopped together. The initial 3.0 release was mostly pure Python in effort to get it out the door. Many parts of the standard library that are written in C are slower than the modules used in the CPython 2.7 counterpart, to this day. It was not and is not being tested. The users are not there to test it either.<p>- Community trust has been broken, I&#x27;m not sure anyone really believes another big break isn&#x27;t incoming regardless of statements to the contrary. The core dev team is going to do what they want and you&#x27;re going to like it, period.<p>- Python3 zealots have done a lot of harm by not accepting valid criticism, and aggressively attacking those who do what is in their best interests (which we should all do, this should not just apply to the CPython core devs), and continue using Python2 all these years. Watch for downvotes instead of countering my points.<p>- The 2020 date is a just a big political stunt and scare tactic. Code will continue working after 2020. As noted, it works better in CPython2 and PyPy today, and likely will in 2021 as well.<p>- Python3 lives off of and is pushed by PSF propaganda. No way around it as there is no innovation involved. Which is what should determine if new technologies are adopted or not.<p>- Usually when people make mistakes, such as Python3&#x27;s existence, or the inability to mix Python2 and 3 code in the same VM- they go back and fix them. That has not happened with CPython3.<p>- Even back in 2014 projects such as Pyston from GvR&#x27;s employer (Dropbox), were Python(2)-only. It&#x27;s still Python2 today, which says it all.<p>All that said about this trainwreck, I&#x27;m in favor of getting back to a single major version of Python for the community. I&#x27;m using 3.5 for a single project myself but I will still plainly state the truth about the Python3 transition. It was a bad idea, for all the wrong reasons to benefit a rogue band of developers who believe since you aren&#x27;t paying them- you as a community do not matter and should shutup and get to porting.<p>I love Python but will eagerly embrace Pythonic language alternatives as more are released. In particular, I&#x27;d love to see a Pythonic Erlang variety similar to Elixir. Or better yet, just a concise, minimum featured version of Python without all the extra. Picking 1 string formatting method would suffice, the basics but done well, stable in feature-set like Go and compiled. Something similar to a Pythonic Lua would suit me and would be the ideal case for a Python-reboot. Making it a subset of Python2 would make a lot of sense.<p>Lesson learned and bottom line is that we should overthrow all BDFLs.<p>[0]<a href="http:&#x2F;&#x2F;learning-python.com&#x2F;books&#x2F;python-changes-2014-plus.html" rel="nofollow">http:&#x2F;&#x2F;learning-python.com&#x2F;books&#x2F;python-changes-2014-plus.ht...</a>