diff options
| author | milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04> | 2008-10-01 14:15:08 +0000 |
|---|---|---|
| committer | milde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04> | 2008-10-01 14:15:08 +0000 |
| commit | ef3fe32bfd340a948b4ea24ea5b9ffd816be3f3e (patch) | |
| tree | 5d760b76e8a2f6a9f07b7c5f95d3a49bec5d2bfb /docs/dev/testing.txt | |
| parent | 904ad354f2a25107f0a83b47dcf358eff5060417 (diff) | |
| download | docutils-ef3fe32bfd340a948b4ea24ea5b9ffd816be3f3e.tar.gz | |
Update Testing doc: since release 0.5, Python 2.1 support is dropped.
git-svn-id: https://svn.code.sf.net/p/docutils/code/trunk/docutils@5657 929543f6-e4f2-0310-98a6-ba3bd3dd1d04
Diffstat (limited to 'docs/dev/testing.txt')
| -rw-r--r-- | docs/dev/testing.txt | 25 |
1 files changed, 12 insertions, 13 deletions
diff --git a/docs/dev/testing.txt b/docs/dev/testing.txt index 36256be24..03f5e651f 100644 --- a/docs/dev/testing.txt +++ b/docs/dev/testing.txt @@ -33,29 +33,28 @@ be sure that you haven't broken anything. From a shell:: Python Versions =============== -The Docutils 0.4 release supports Python 2.1 [#py21]_ or later, with -some features only working (and being tested) with Python 2.3+. -Therefore, you should actually have Pythons 2.1 [#py21]_, 2.2, 2.3, as -well as the latest Python installed and always run the tests on all of -them. (A good way to do that is to always run the test suite through -a short script that runs ``alltests.py`` under each version of -Python.) If you can't afford intalling 3 or more Python versions, the -edge cases (2.1 and 2.3) should cover most of it. - -.. [#py21] Python 2.1 may be used providing the compiler package is - installed. The compiler package can be found in the Tools/ - directory of Python 2.1's source distribution. +The Docutils 0.5 release supports Python 2.2 or later, with some features +only working (and being tested) with Python >= 2.3. Therefore, you should +actually have Pythons 2.2, 2.3, as well as the latest Python (2.5 at the time +of this writing) installed and always run the tests on all of them. (A good +way to do that is to always run the test suite through a short script that +runs ``alltests.py`` under each version of Python.) If you can't afford +intalling 3 or more Python versions, the edge cases (2.2 and 2.3) should +cover most of it. Good resources covering the differences between Python versions: * `What's New in Python 2.2`__ * `What's New in Python 2.3`__ * `What's New in Python 2.4`__ +* `What's New in Python 2.5`__ +* latest `What's New in Python`__ * `PEP 290 - Code Migration and Modernization`__ __ http://www.python.org/doc/2.2.3/whatsnew/whatsnew22.html __ http://www.python.org/doc/2.3.5/whatsnew/whatsnew23.html -__ http://www.python.org/doc/2.4.1/whatsnew/whatsnew24.html +__ http://www.python.org/doc/2.4.4/whatsnew/whatsnew24.html +__ http://www.python.org/doc/2.5.2/whatsnew/whatsnew25.html __ http://www.python.org/peps/pep-0290.html .. _Python Check-in Policies: http://www.python.org/dev/tools.html |