3 ms·

You can see some reasons from one of the core developers here [0]: "We (i.e. the Python core developers) predicted when Python 3.0 was released that it would t

You can see some reasons from one of the core developers here [0]: "We (i.e. the Python core developers) predicted when Python 3.0 was released that it would take about 5 years for 3.x to become the "default" choice for new projects over the 2.x series." He suggests the 5 year timeline begins in June 2009 with the release of 3.1 (since 3.0 still had many bugs) - so that means there is a little more than half a year left for it to become the default, if the prediction holds true. The rest of his post goes into the issues in adopting Python 3.x. [0]: http://programmers.stackexchange.com/questions/63859/why-do-people-hesitate-to-use-python-3 http://programmers.stackexchange.com/questions/63859/why-do-...

vdaniuk 13y ago
Thanks for sharing this information. I am interested what strategies can be applied to increase the speed of language adoption.
- 16s 13y ago
  There are large working Python 2 code bases in a lot of organizations. It works great. Fabulously reliable. Extremely well-tested. Been running great for years. They have no desire or need to upgrade and will run Python 2 and pay devs to maintain it forever. Welcome to the real world.
  - SeanDav 13y ago
    You are right, just as there are still COBOL applications around.
- bru 13y ago
  > what strategies can be applied to increase the speed of language adoption. In the case of Python 3, a neat thing library developers can do is write code that is both valid for Python 2 and Python 3. The six[0] library is a wrapper for making code compatible with both versions. There are tools like 2to3[1] and 3to2[2] that convert code from one version to another. They're not perfect but do catch the most common differences. Such things help with making the change. However it is the availability (or more exactly lack of) of famous and widely used libraries that hinder or speed up the adoption. For example, Django recently started offering a Python 3 version[0]. Numpy and Scipy support it since around 2011 only. 0: http://pythonhosted.org/six http://pythonhosted.org/six 1: http://docs.python.org/2/library/2to3.html http://docs.python.org/2/library/2to3.html 2: https://wiki.python.org/moin/3to2 https://wiki.python.org/moin/3to2 3: "Porting to Python 3" htthttp://pythonhosted.org/sixps://docs.djangoproject.com/en/dev/topics/python3/ http://pythonhosted.org/sixps://docs.djangoproject.com/en/de... >Django 1.5 is the first version of Django to support Python 3. The same code runs both on Python 2 (≥ 2.6.5) and Python 3 (≥ 3.2), thanks to the six compatibility layer. "Django's future, and Python 3" https://www.djangoproject.com/weblog/2012/mar/13/py3k/ https://www.djangoproject.com/weblog/2012/mar/13/py3k/

vdaniuk 13y ago

Thanks for sharing this information. I am interested what strategies can be applied to increase the speed of language adoption.

16s 13y ago
There are large working Python 2 code bases in a lot of organizations. It works great. Fabulously reliable. Extremely well-tested. Been running great for years. They have no desire or need to upgrade and will run Python 2 and pay devs to maintain it forever. Welcome to the real world.
- SeanDav 13y ago
  You are right, just as there are still COBOL applications around.
bru 13y ago
> what strategies can be applied to increase the speed of language adoption. In the case of Python 3, a neat thing library developers can do is write code that is both valid for Python 2 and Python 3. The six[0] library is a wrapper for making code compatible with both versions. There are tools like 2to3[1] and 3to2[2] that convert code from one version to another. They're not perfect but do catch the most common differences. Such things help with making the change. However it is the availability (or more exactly lack of) of famous and widely used libraries that hinder or speed up the adoption. For example, Django recently started offering a Python 3 version[0]. Numpy and Scipy support it since around 2011 only. 0: http://pythonhosted.org/six http://pythonhosted.org/six 1: http://docs.python.org/2/library/2to3.html http://docs.python.org/2/library/2to3.html 2: https://wiki.python.org/moin/3to2 https://wiki.python.org/moin/3to2 3: "Porting to Python 3" htthttp://pythonhosted.org/sixps://docs.djangoproject.com/en/dev/topics/python3/ http://pythonhosted.org/sixps://docs.djangoproject.com/en/de... >Django 1.5 is the first version of Django to support Python 3. The same code runs both on Python 2 (≥ 2.6.5) and Python 3 (≥ 3.2), thanks to the six compatibility layer. "Django's future, and Python 3" https://www.djangoproject.com/weblog/2012/mar/13/py3k/ https://www.djangoproject.com/weblog/2012/mar/13/py3k/