| 1 |
title: Release Notes for v2.2 |
| 2 |
|
| 3 |
Python-Markdown 2.2 Release Notes |
| 4 |
================================= |
| 5 |
|
| 6 |
We are pleased to release Python-Markdown 2.2 which makes improvements on 2.1. |
| 7 |
While 2.2 is primarily a bug fix release, some internal improvements were made |
| 8 |
to the parser, and a few security issues were resolved. |
| 9 |
|
| 10 |
Python-Markdown supports Python versions 2.5, 2.6, 2.7, 3.1, and 3.2 out |
| 11 |
of the box. |
| 12 |
|
| 13 |
Backwards-incompatible Changes |
| 14 |
------------------------------ |
| 15 |
|
| 16 |
While Python-Markdown has received only minor internal changes since the last |
| 17 |
release, there are a few backward-incompatible changes to note: |
| 18 |
|
| 19 |
* Support had been dropped for Python 2.4. No guarantees are made that the |
| 20 |
library will work in any version of Python lower than 2.5. Additionally, while |
| 21 |
the library had been tested with Python 2.5, consider Python 2.5 support to be |
| 22 |
depreciated. It is not likely that any future versions will continue to |
| 23 |
support any version of Python less than 2.6. |
| 24 |
|
| 25 |
* For many years Python-Markdown has identified `<ins>` and `<del>` tags in raw |
| 26 |
HTML input as block level tags. As they are actually inline level tags, this |
| 27 |
behavior has been changed. This may result in slightly different output. While |
| 28 |
in most cases, the new output is more correct, there may be a few edge cases |
| 29 |
where a document author has relied on the previous incorrect behavior. It is |
| 30 |
likely that a few adjustments may need to be made to those documents. |
| 31 |
|
| 32 |
* The behavior of the `enable_attributes` keyword has been slightly altered. If |
| 33 |
authors have been using attributes in documents with `safe_mode` on, those |
| 34 |
attributes will no longer be parsed unless `enable_attributes` is explicitly |
| 35 |
set to `True`. This change was made to prevent untrusted authors from |
| 36 |
injecting potentially harmful JavaScript in documents. This change had no |
| 37 |
effect when not in `safe_mode`. |
| 38 |
|
| 39 |
What's New in Python-Markdown 2.2 |
| 40 |
--------------------------------- |
| 41 |
|
| 42 |
The docs were refactored and can now be found at |
| 43 |
`http://packages.python.org/Markdown/`. The docs are now maintained in the |
| 44 |
Repository and are generated by the `setup.py build_docs` command. |
| 45 |
|
| 46 |
The [Sane_Lists](../extensions/sane_lists.md) |
| 47 |
extension was added. The Sane Lists Extension alters the behavior of the |
| 48 |
Markdown List syntax to be less surprising by not allowing the mixing of list |
| 49 |
types. In other words, an ordered list will not continue when an unordered list |
| 50 |
item is encountered and vice versa. |
| 51 |
|
| 52 |
Markdown now excepts a full path to an extension module. In other words, your |
| 53 |
extensions no longer need to be in the primary namespace (and start with `mdx_`) |
| 54 |
for Markdown to find them. Just do `Markdown(extension=['path.to.some.module'])`. |
| 55 |
As long as the provided module contains a compatible extension, the extension |
| 56 |
will be loaded. |
| 57 |
|
| 58 |
The BlockParser API was slightly altered to allow `blockprocessor.run` to return |
| 59 |
`True` or `False` which provides more control to the block processor loop from |
| 60 |
within any Blockprocessor instance. |
| 61 |
|
| 62 |
Various bug fixes have been made. See the |
| 63 |
[commit log](https://github.com/Python-Markdown/markdown/commits/master) |
| 64 |
for a complete history of the changes. |