From 7e7e3d02e657101ef902b257f7b586ab4a231315 Mon Sep 17 00:00:00 2001 From: Markus Unterwaditzer Date: Sat, 29 Jun 2013 20:18:17 +0200 Subject: [PATCH] Rewrite section on choosing a Python version --- docs/starting/which-python.rst | 39 +++++++++++++++------------------- 1 file changed, 17 insertions(+), 22 deletions(-) diff --git a/docs/starting/which-python.rst b/docs/starting/which-python.rst index 7c995ac83..e07ad4bc1 100644 --- a/docs/starting/which-python.rst +++ b/docs/starting/which-python.rst @@ -3,37 +3,32 @@ Picking an Interpreter .. _which-python: -Which Python to use? - - -2.x vs 3.x -~~~~~~~~~~ - - Python 2.x is the status quo, Python 3.x is the shiny new thing. - - -`Further Reading `_ - - -Today ------ +Today (Python 2) +~~~~~~~~~~~~~~~~ If you're choosing a Python interpreter to use, I *highly* recommend you use Python 2.7.x, unless you have a strong reason not to. +Also use Python 2.7.x if you're starting to work on a new Python module. If you +have managed to get it working on 2.7, you can add support for older 2.x +versions. -The Future ----------- +The Future (Python 3) +~~~~~~~~~~~~~~~~~~~~~ -As more and more modules get ported over to Python3, the easier it will be for -others to use it. + Python 2.x is the status quo, Python 3.x is the shiny new thing. +`Further Reading `_ -Which Python to Support? -~~~~~~~~~~~~~~~~~~~~~~~~ +Python 3, on the other hand, differs much more greatly from Python 2, so +writing code that works both on Python 2 and Python 3 is a very complicated +process. -If you're starting work on a new Python module, I recommend you write it for -Python 2.5 or 2.6, and add support for Python3 in a later iteration. +It is still possible to `write code that works on Python 2.6, 2.7 and 3.3 +`_. Depending on +the kind of software you are writing, this might be either tricky or extremely +hard, and if you're a beginner there are much more important things to worry +about. Implementations ~~~~~~~~~~~~~~~