At PyCon Ireland 2010, Paul described his experience of working with Python 3 in creating O'Reilly's Head First Programming and Head First Python (both of which target Python 3). As a big fan of Python 3, Paul suggested that all Python 2 programmers needed to at least try Python 3 as soon as was practical, if not embrace it for all "new" work. In this talk, Paul provides an update on the current status of Python 3 and discusses the community's adoption (or lack of) the latest version of the Python programming language, talking about what has changed in the year and a bit since last year, as well as describing his own experience of working with Python on recent consultancy projects.
15. What do the good folk at python.org have to say?
15
16. Point #1 - Use 2 instead of 3
“... if you're deploying to an environment you don't
control, that may impose a specific version rather
than allowing you a free selection from the
available versions.”
16
17. I recently worked on a project that unashamedly
specified Python 2.6.4 as the target platform
(even though the work was XML-based)
17
18. Point #2 - Use 2 instead of 3
“... if you want to use a specific third party
package or utility that doesn't yet have a released
version that is compatible with Python 3, and
porting that package is a non-trivial task...”
18
19. Another project (wisely) selected Django as
the target web-dev platform... which meant more
work for me in Python 2.x
19
20. Point #3 - Use 2 instead of 3
“... if you wish to use an alternative
implementation of Python such as IronPython,
Jython or PyPy...”
20
21. A third project specified the .NET platform,
but didn't care which language I used...
21
22. A third project specified the .NET platform,
but didn't care which language I used...
I used IronPython and was restricted
to working with the 2.7 release of Python
22