S
Steven D'Aprano
Today in Montreal Canada, there was a Language Summit to discuss the
future of Python. Some highlights:
PyPy is only three bug fixes away from shipping support for Python 3.2!
Guido confirms that easing the transition from 2.x to 3.x code is a major
priority. Version 2.7 is alive and in good health and not ready to be
retired yet, but he's still against releasing a version 2.8.
Both IronPython and Jython hope to support Python 3 soon, Jython is being
held back by a lack of contributors.
Packaging is hard. Very hard. There is a lot of work going on to try to
improve packaging.
After five years experience in managing the transition between 2 and 3,
the official recommendation is now the opposite of what it was five years
ago: write a single code-base aimed at both 2 and 3, rather than trying
to automate translation via 2to3 or other tools.
There is a lot of interest for optional type checking.
More in this email thread here:
https://mail.python.org/pipermail/python-dev/2014-April/133873.html
future of Python. Some highlights:
PyPy is only three bug fixes away from shipping support for Python 3.2!
Guido confirms that easing the transition from 2.x to 3.x code is a major
priority. Version 2.7 is alive and in good health and not ready to be
retired yet, but he's still against releasing a version 2.8.
Both IronPython and Jython hope to support Python 3 soon, Jython is being
held back by a lack of contributors.
Packaging is hard. Very hard. There is a lot of work going on to try to
improve packaging.
After five years experience in managing the transition between 2 and 3,
the official recommendation is now the opposite of what it was five years
ago: write a single code-base aimed at both 2 and 3, rather than trying
to automate translation via 2to3 or other tools.
There is a lot of interest for optional type checking.
More in this email thread here:
https://mail.python.org/pipermail/python-dev/2014-April/133873.html