Skip to main content

Python 2.7 vs 3.6 in 2018

Python 3 now has 75% adoption and Python 2 has 25%, at least according to the Python developers survey 2017 referenced on Python.org,  however google trends doesn't seem to show this.



The following graph is from google trends, comparing 2.7 vs 3.4, 3.5, 3.6, and 3.7. I would expect to see a much greater difference if 2.7 has only 25% usage.


It does appear in the end of the 12 month graph that Python 3.6 is finally about to surpass 2.7, but has not yet done so. The 5 year trend shows that both 2.7 and 3.6 are both growing but 3.6 is catching up quickly. 


It's interesting that the data in the latest report does not seem to correlate to the 5 year graph. While "in 2016 60% were using Python 2 compared with 40% for python 3" is clearly shown in the graph,  the latest report of 75% using python 3 vs 25% using python 2 does not appear to be accurate. It appears to be more of a 50% - 50% or 40% - 60% split if you account for all the python 3 versions.

I use duck duck go, and Python 2.7 results still always show up first. What do you think? Did 3.x finally actually pass 2.7? What explains the disparity between the report and google trends data?

If you're wondering, I use both versions.

Comments

  1. My guess is that although people are preferring Python 3 for new development, the majority of *running* software is still on Python 2. The PyPI download statistics should be a good indication of the latter: you can query them at https://bigquery.cloud.google.com/dataset/the-psf:pypi?pli=1 :

    SELECT
    substr(details.implementation.version, 0, 3) as ver,
    COUNT(*) as downloads,
    FROM
    TABLE_DATE_RANGE(
    [the-psf:pypi.downloads],
    TIMESTAMP("20180401"),
    TIMESTAMP("20180407"))
    GROUP BY ver order by downloads desc

    1 2.7 96835255
    2 3.6 19353614
    3 null 18605539
    4 3.5 10602418
    5 3.4 4737409
    6 2.6 940158
    7 2.4 146161
    8 3.7 107378

    Compared to the same period in 2017:

    1 2.7 100867390
    2 null 35321706
    3 3.5 9847261
    4 3.4 5853988
    5 3.6 4433603
    6 2.6 3319993
    7 3.3 294804
    8 2.4 106793

    ReplyDelete

Post a Comment

Popular posts from this blog

Kivy vs React-Native for building cross platform mobile apps

I've built three apps now using Kivy and one with React-Native, just wanted to share my thoughts on both. Just a warning, I am strongly biased towards python and this is all based on opinion and experience and is thus worth what you pay for it. I don't claim to be an expert in either of these, just have worked with each for several months.  If something is incorrect I'd love to hear advice. Kivy Demo of one of the apps Pros: Nice to be able to run natively on the desktop WITHOUT a simulator Python is easy to work with Use (almost) any python library Very easy to create custom widgets Kivy properties and data binding just work. Way nicer than React's "state" / flux / redux whatever you want to call it (stupid?).  Native interfaces (pyjnius) and (pyobjc) Runs and feels pretty smooth Cons: Default widget toolkit looks like Android 4.4. Requiring you use your own widgets or a theming kit like KivyMD  if styling bothers you Creating dy

Control Systems in Python - Part 1 - Bode and Step Response

I hate matlab with passion, yet sadly, nearly everyone uses it.  I'm a fan of Python and open source stuff so here's a simple article on how to do some common control systems stuff in Python. First we need to make sure the environment is setup. Install IPython (or you can use any other python shell, but a unicode supported shell is preferred) Install python-control (numpy, scipy) Install sympy These should do if your on Ubuntu/debian: sudo apt - get install python - sympy python-numpy python-scipy python-matplotlib ipython Then you need to install python control, see How to download and install python-control Intro to using Sympy Open ipython and run the following: import sympy from sympy import * sympy.init_printing() s = Symbol('s') Now we can do things like define transfer functions using the symbolic variable s. We can expand the bottom using the .simplify() method and we can do something more complex like... which is really nice because it