/usr/share/doc/python-markdown-doc/docs/release-2.1.0.html is in python-markdown-doc 2.6.9-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 | <!DOCTYPE html>
<html>
<head>
<meta charset=utf-8>
<title>Release Notes for v2.1.0 — Python Markdown</title>
<link rel="stylesheet" href="default.css" type="text/css">
</head>
<body>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="siteindex.html" title="General Index">index</a></li>
<li class="right">
<a href="release-2.0.2.html" title="Release Notes for v2.0.2"
accesskey="N">next</a> |</li>
<li class="right">
<a href="release-2.1.1.html" title="Release Notes for v2.1.1"
accesskey="P">previous</a> |</li>
<li><img src="py.png" alt=""
style="vertical-align: middle; margin-top: -1px"/></li>
<li><a href="index.html">Python Markdown v2.6.9 documentation</a> »</li>
<li><a href="release-2.1.0.html">Release Notes for v2.1.0</a> »</li>
</ul>
</div> <!-- .related -->
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<h1 id="python-markdown-210-release-notes">Python-Markdown 2.1.0 Release Notes<a class="headerlink" href="#python-markdown-210-release-notes" title="Permanent link">¶</a></h1>
<p>We are pleased to release Python-Markdown 2.1 which makes many
improvements on 2.0. In fact, we consider 2.1 to be what 2.0 should have been.
While 2.1 consists mostly of bug fixes, bringing Python-Markdown more inline
with other implementations, some internal improvements were made to the parser,
a few new built-in extensions were added, and HTML5 support was added.</p>
<p>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 code base installs on Python 3.1 and 3.2 with no
extra work by the end user.</p>
<h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="headerlink" href="#backwards-incompatible-changes" title="Permanent link">¶</a></h2>
<p>While Python-Markdown has received only minor internal changes since the last
release, there are a few backward-incompatible changes to note:</p>
<ul>
<li>
<p>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.</p>
</li>
<li>
<p>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
removed in a future version. All users are encouraged to use keyword arguments
as documented in the <a href="reference.html">Library Reference</a>.</p>
</li>
<li>
<p>Past versions of Python-Markdown provided module level Global variables which
controlled the behavior of a few different aspects of the parser. Those global
variables have been replaced with attributes on the Markdown class.
Additionally, those attributes are settable as keyword arguments when
initializing a class instance. Therefore, if you were editing the global
variables (either by editing the source or by overriding them in your code),
you should now set them on the class. See the
<a href="reference.html">Library Reference</a> for the options available.</p>
</li>
<li>
<p>If you have been using the <a href="extensions/header_id.html">HeaderId</a> extension
to define custom ids on headers, you will want to switch to using the new
<a href="extensions/attr_list.html">Attribute List</a> extension. The HeaderId extension
now only auto-generates ids on headers which have not already had ids defined.
Note that the <a href="extensions/extra.html">Extra</a> extension has been switched to use
Attribute Lists instead of HeaderId as it did previously.</p>
</li>
<li>
<p>Some code was moved into the <code>markdown.util</code> namespace which was previously
in the <code>markdown</code> namespace. Extension authors may need to adjust a few
import statements in their extensions to work with the changes.</p>
</li>
<li>
<p>The command line script name was changed to <code>markdown_py</code>. The previous name
(<code>markdown</code>) was conflicting with people (and Linux package systems) who also
had markdown.pl installed on there system as markdown.pl’s command line script
was also named <code>markdown</code>. Be aware that installing Python-Markdown 2.1
will not remove the old versions of the script with different names. You
may want to remove them yourself as they are unlikely to work properly.</p>
</li>
</ul>
<h2 id="whats-new-in-python-markdown-21">What’s New in Python-Markdown 2.1<a class="headerlink" href="#whats-new-in-python-markdown-21" title="Permanent link">¶</a></h2>
<p>Three new extensions were added. <a href="extensions/attr_list.html">Attribute Lists</a>,
which was inspired by Maruku’s feature of the same name,
<a href="extensions/nl2br.html">Newline to Break</a>, which was inspired by GitHub
Flavored Markdown, and <a href="extensions/smart_strong.html">Smart Strong</a>, which
fills a hole in the Extra extension.</p>
<p>HTML5 is now supported. All this really means is that new block level elements
introduced in the HTML5 spec are now properly recognized as raw HTML. As
valid HTML5 can consist of either HTML4 or XHTML1, there is no need to add a
new HTML5 serializers. That said, <code>html5</code> and <code>xhtml5</code> have been added as
aliases of the <code>html4</code> and <code>xhtml1</code> serializers respectively.</p>
<p>An XHTML serializer has been added. Previously, ElementTree’s XML serializer
was being used for XHTML output. With the new serializer we are able to avoid
more invalid output like empty elements (i.e., <code><p /></code>) which can choke
browsers.</p>
<p>Improved support for Python 3.x. Now when running <code>setupy.py install</code> in
Python 3.1 or greater the 2to3 tool is run automatically. 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.</p>
<p>Methods on instances of the Markdown class that do not return results can now
be changed allowing one to do <code>md.reset().convert(moretext)</code>.</p>
<p>The Markdown class was refactored so that a subclass could define it’s own
<code>build_parser</code> method which would build a completely different parser. In
other words, one could use the basic machinery in the markdown library to
build a parser of a different markup language without the overhead of building
the markdown parser and throwing it away.</p>
<p>Import statements within markdown have been improved so that third party
libraries can embed the markdown library if they desire (licensing permitting).</p>
<p>Added support for Python’s <code>-m</code> command line option. You can run the markdown
package as a command line script. Do <code>python -m markdown [options] [args]</code>.
Note that this is only fully supported in Python 2.7+. Python 2.5 & 2.6
require you to call the module directly (<code>markdown.__main__</code>) rather than
the package (<code>markdown</code>). This does not work in Python 2.4.</p>
<p>The command line script has been renamed to <code>markdown_py</code> which avoids all the
various problems we had with previous names. Also improved the command line
script to accept input on <code>stdin</code>.</p>
<p>The testing framework has been completely rebuilt using the Nose testing
framework. This provides a number of benefits including the ability to better
test the built-in extensions and other options available to change the parsing
behavior. See the <a href="test_suite.html">Test Suite</a> documentation for details.</p>
<p>Various bug fixes have been made, which are too numerous to list here. See the
<a href="https://github.com/Python-Markdown/markdown/commits/master">commit log</a> for a
complete history of the changes.</p>
</div> <!-- .body -->
</div> <!-- .bodywrapper -->
</div> <!-- .documentwrapper -->
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3>Table Of Contents</h3>
<div class="toc">
<ul>
<li><a href="#python-markdown-210-release-notes">Python-Markdown 2.1.0 Release Notes</a><ul>
<li><a href="#backwards-incompatible-changes">Backwards-incompatible Changes</a></li>
<li><a href="#whats-new-in-python-markdown-21">What's New in Python-Markdown 2.1</a></li>
</ul>
</li>
</ul>
</div>
<h4>Previous topic</h4>
<p class="topless"><a href="release-2.1.1.html"
title="previous chapter">Release Notes for v2.1.1</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="release-2.0.2.html"
title="next chapter">Release Notes for v2.0.2</a></p>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="https://github.com/Python-Markdown/markdown/issues"
>Report a Bug</a></li>
<li><a href="release-2.1.0.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div> <!-- .sphinxsidebarwrapper -->
</div> <!-- .sphinxsidebar -->
<div class="clearer"></div>
</div> <!-- .document -->
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="siteindex.html" title="General Index">index</a></li>
<li class="right">
<a href="release-2.0.2.html" title="Release Notes for v2.0.2"
accesskey="N">next</a> |</li>
<li class="right">
<a href="release-2.1.1.html" title="Release Notes for v2.1.1"
accesskey="P">previous</a> |</li>
<li><img src="py.png" alt=""
style="vertical-align: middle; margin-top: -1px"/></li>
<li><a href="index.html">Python Markdown v2.6.9 documentation</a> »</li>
<li><a href="release-2.1.0.html">Release Notes for v2.1.0</a> »</li>
</ul>
</div> <!-- .related -->
<div class="footer">© 2010-2012 Python Markdown Project</div>
</body>
</html>
|