diff options
Diffstat (limited to 'docs/release-2.1.0-alpha.txt')
| -rw-r--r-- | docs/release-2.1.0-alpha.txt | 22 |
1 files changed, 15 insertions, 7 deletions
diff --git a/docs/release-2.1.0-alpha.txt b/docs/release-2.1.0-alpha.txt index fe65b4b..5fb6ac7 100644 --- a/docs/release-2.1.0-alpha.txt +++ b/docs/release-2.1.0-alpha.txt @@ -10,9 +10,9 @@ a few new builtin extensions were added, and HTML5 support was added. Please be aware that Python-Markdown 2.1-Alpha is *alpha* software and is not considered production ready pending the release of 2.1-Final. -Python-Markdown supports Python versions 2.4, 2.5, 2.6, 2.7, and 3.1 out of the -box. In fact, the same codebase installs on Python 3.1 with no extra work by -the end user. +Python-Markdown supports Python versions 2.4, 2.5, 2.6, 2.7, 3.1, and 3.2 out of +the box. In fact, the same codebase installs on Python 3.1 and 3.2 with no extra +work by the end user. Backwards-incompatible Changes ------------------------------ @@ -20,6 +20,14 @@ Backwards-incompatible Changes While Python-Markdown has received only minor internal changes since the last release, there are a few backward-incompatible changes to note: +* Support had been dropped for Python 2.3. No guarantees are made that the library +will work in any version of Python lower than 2.4. Additionally, while the library +had been tested with Python 2.4, consider Python 2.4 support to be depreciated. +It is not likely that any future versions will continue to support any version of +Python less than 2.5. Note that Python 3.0 is not supported due to a bug in its +2to3 tool. If you must use Python-Markdown with Python 3.0, it is suggested you +manually use Python 3.1's 2to3 tool to do a conversion. + * Python-Markdown previously accepted positional arguments on its class and wrapper methods. It now expects keyword arguments. Currently, the positional arguments should continue to work, but the solution feels hacky and may be @@ -35,10 +43,10 @@ variables (either by editing the source or by overriding them in your code), you should now set them on the class. See [[using_as_module]] for the options available. -* If you have been using the HeaderID extension to define custom ids on headers, -you will want to swtich to using the new attr_list extension. The headerid +* If you have been using the [[HeaderID]] extension to define custom ids on headers, +you will want to switch to using the new [[attr_list]] extension. The headerid extension now only auto-generates ids on headers which have not already had -ids defined. Note that the extra extension has been switched to use attr_list +ids defined. Note that the [[extra]] extension has been switched to use attr_list instead of headeris as it did previously. * Some code was moved into the `markdown.util` namespace which was previously @@ -100,4 +108,4 @@ behavior. See the [[test_suite]] documentation for details. Various bug fixes have been made, which are too numerous to list here. See the [commit log](https://github.com/waylan/Python-Markdown/commits/master) for a -complete history of the changes. +complete history of the changes.
\ No newline at end of file |