Skip to content

Commit 1a77ee0

Browse files
committed
Deployed 2398565 with MkDocs version: 0.17.2
1 parent de01026 commit 1a77ee0

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+2124
-2110
lines changed

404.html

100755100644
+1-1
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ <h3>Navigation</h3>
106106

107107
<!--
108108
MkDocs version : 0.17.2
109-
Docs Build Date UTC : 2017-12-06 21:11:39
109+
Docs Build Date UTC : 2017-12-06 23:52:10
110110
-->
111111
</body>
112112
</html>

authors/index.html

100755100644
+1-1
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ <h3>Navigation</h3>
213213

214214
<!--
215215
MkDocs version : 0.17.2
216-
Docs Build Date UTC : 2017-12-06 21:11:41
216+
Docs Build Date UTC : 2017-12-06 23:52:12
217217
-->
218218
</body>
219219
</html>

change_log/index.html

100755100644
+1-1
Original file line numberDiff line numberDiff line change
@@ -307,7 +307,7 @@ <h3>Navigation</h3>
307307

308308
<!--
309309
MkDocs version : 0.17.2
310-
Docs Build Date UTC : 2017-12-06 21:11:41
310+
Docs Build Date UTC : 2017-12-06 23:52:12
311311
-->
312312
</body>
313313
</html>

change_log/release-2.0/index.html

100755100644
+1-1
Original file line numberDiff line numberDiff line change
@@ -223,7 +223,7 @@ <h3>Navigation</h3>
223223

224224
<!--
225225
MkDocs version : 0.17.2
226-
Docs Build Date UTC : 2017-12-06 21:11:41
226+
Docs Build Date UTC : 2017-12-06 23:52:12
227227
-->
228228
</body>
229229
</html>

change_log/release-2.1/index.html

100755100644
+47-46
Original file line numberDiff line numberDiff line change
@@ -67,50 +67,50 @@ <h3>Navigation</h3>
6767
<div class="documentwrapper">
6868
<div class="bodywrapper">
6969
<div class="body" role="main"><h1 id="python-markdown-21-release-notes">Python-Markdown 2.1 Release Notes<a class="headerlink" href="#python-markdown-21-release-notes" title="Permanent link">&para;</a></h1>
70-
<p>We are pleased to release Python-Markdown 2.1 which makes many
71-
improvements on 2.0. In fact, we consider 2.1 to be what 2.0 should have been.
72-
While 2.1 consists mostly of bug fixes, bringing Python-Markdown more inline
73-
with other implementations, some internal improvements were made to the parser,
70+
<p>We are pleased to release Python-Markdown 2.1 which makes many
71+
improvements on 2.0. In fact, we consider 2.1 to be what 2.0 should have been.
72+
While 2.1 consists mostly of bug fixes, bringing Python-Markdown more inline
73+
with other implementations, some internal improvements were made to the parser,
7474
a few new built-in extensions were added, and HTML5 support was added.</p>
75-
<p>Python-Markdown supports Python versions 2.4, 2.5, 2.6, 2.7, 3.1, and 3.2 out
76-
of the box. In fact, the same code base installs on Python 3.1 and 3.2 with no
75+
<p>Python-Markdown supports Python versions 2.4, 2.5, 2.6, 2.7, 3.1, and 3.2 out
76+
of the box. In fact, the same code base installs on Python 3.1 and 3.2 with no
7777
extra work by the end user.</p>
7878
<h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="headerlink" href="#backwards-incompatible-changes" title="Permanent link">&para;</a></h2>
7979
<p>While Python-Markdown has received only minor internal changes since the last
8080
release, there are a few backward-incompatible changes to note:</p>
8181
<ul>
8282
<li>
83-
<p>Support had been dropped for Python 2.3. No guarantees are made that the
84-
library will work in any version of Python lower than 2.4. Additionally, while
85-
the library had been tested with Python 2.4, consider Python 2.4 support to be
83+
<p>Support had been dropped for Python 2.3. No guarantees are made that the
84+
library will work in any version of Python lower than 2.4. Additionally, while
85+
the library had been tested with Python 2.4, consider Python 2.4 support to be
8686
depreciated. It is not likely that any future versions will continue to support
87-
any version of Python less than 2.5. Note that Python 3.0 is not supported due
88-
to a bug in its 2to3 tool. If you must use Python-Markdown with Python 3.0, it
87+
any version of Python less than 2.5. Note that Python 3.0 is not supported due
88+
to a bug in its 2to3 tool. If you must use Python-Markdown with Python 3.0, it
8989
is suggested you manually use Python 3.1&rsquo;s 2to3 tool to do a conversion.</p>
9090
</li>
9191
<li>
9292
<p>Python-Markdown previously accepted positional arguments on its class and
9393
wrapper methods. It now expects keyword arguments. Currently, the positional
94-
arguments should continue to work, but the solution feels hacky and may be
95-
removed in a future version. All users are encouraged to use keyword arguments
94+
arguments should continue to work, but the solution feels hacky and may be
95+
removed in a future version. All users are encouraged to use keyword arguments
9696
as documented in the <a href="../../reference/">Library Reference</a>.</p>
9797
</li>
9898
<li>
9999
<p>Past versions of Python-Markdown provided module level Global variables which
100100
controlled the behavior of a few different aspects of the parser. Those global
101-
variables have been replaced with attributes on the Markdown class.
102-
Additionally, those attributes are settable as keyword arguments when
103-
initializing a class instance. Therefore, if you were editing the global
104-
variables (either by editing the source or by overriding them in your code),
105-
you should now set them on the class. See the
101+
variables have been replaced with attributes on the Markdown class.
102+
Additionally, those attributes are settable as keyword arguments when
103+
initializing a class instance. Therefore, if you were editing the global
104+
variables (either by editing the source or by overriding them in your code),
105+
you should now set them on the class. See the
106106
<a href="../../reference/">Library Reference</a> for the options available.</p>
107107
</li>
108108
<li>
109-
<p>If you have been using the HeaderId extension
110-
to define custom ids on headers, you will want to switch to using the new
111-
Attribute List extension. The HeaderId extension
112-
now only auto-generates ids on headers which have not already had ids defined.
113-
Note that the Extra extension has been switched to use
109+
<p>If you have been using the <a href="../extensions.md">HeaderId</a> extension
110+
to define custom ids on headers, you will want to switch to using the new
111+
<a href="../../extensions/attr_list/">Attribute List</a> extension. The HeaderId extension
112+
now only auto-generates ids on headers which have not already had ids defined.
113+
Note that the <a href="../../extensions/extra/">Extra</a> extension has been switched to use
114114
Attribute Lists instead of HeaderId as it did previously.</p>
115115
</li>
116116
<li>
@@ -128,47 +128,48 @@ <h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="
128128
</li>
129129
</ul>
130130
<h2 id="whats-new-in-python-markdown-21">What&rsquo;s New in Python-Markdown 2.1<a class="headerlink" href="#whats-new-in-python-markdown-21" title="Permanent link">&para;</a></h2>
131-
<p>Three new extensions were added. Attribute Lists,
132-
which was inspired by Maruku&rsquo;s feature of the same name,
133-
Newline to Break, which was inspired by GitHub
134-
Flavored Markdown, and Smart Strong, which
131+
<p>Three new extensions were added. <a href="../../extensions/attr_list/">Attribute Lists</a>,
132+
which was inspired by Maruku&rsquo;s feature of the same name,
133+
<a href="../../extensions/nl2br/">Newline to Break</a>, which was inspired by GitHub
134+
Flavored Markdown, and <a href="../../extensions/smart_strong/">Smart Strong</a>, which
135135
fills a hole in the Extra extension.</p>
136-
<p>HTML5 is now supported. All this really means is that new block level elements
136+
<p>HTML5 is now supported. All this really means is that new block level elements
137137
introduced in the HTML5 spec are now properly recognized as raw HTML. As
138138
valid HTML5 can consist of either HTML4 or XHTML1, there is no need to add a
139-
new HTML5 serializers. That said, <code>html5</code> and <code>xhtml5</code> have been added as
139+
new HTML5 serializers. That said, <code>html5</code> and <code>xhtml5</code> have been added as
140140
aliases of the <code>html4</code> and <code>xhtml1</code> serializers respectively.</p>
141-
<p>An XHTML serializer has been added. Previously, ElementTree&rsquo;s XML serializer
141+
<p>An XHTML serializer has been added. Previously, ElementTree&rsquo;s XML serializer
142142
was being used for XHTML output. With the new serializer we are able to avoid
143-
more invalid output like empty elements (i.e., <code>&lt;p /&gt;</code>) which can choke
143+
more invalid output like empty elements (i.e., <code>&lt;p /&gt;</code>) which can choke
144144
browsers.</p>
145-
<p>Improved support for Python 3.x. Now when running <code>setupy.py install</code> in
146-
Python 3.1 or greater the 2to3 tool is run automatically. Note that Python 3.0
145+
<p>Improved support for Python 3.x. Now when running <code>setupy.py install</code> in
146+
Python 3.1 or greater the 2to3 tool is run automatically. Note that Python 3.0
147147
is not supported due to a bug in its 2to3 tool. If you must use Python-Markdown
148148
with Python 3.0, it is suggested you manually use Python 3.1&rsquo;s 2to3 tool to
149149
do a conversion.</p>
150150
<p>Methods on instances of the Markdown class that do not return results can now
151151
be changed allowing one to do <code>md.reset().convert(moretext)</code>.</p>
152-
<p>The Markdown class was refactored so that a subclass could define it&rsquo;s own <code>build_parser</code> method which would build a completely different parser. In
153-
other words, one could use the basic machinery in the markdown library to
152+
<p>The Markdown class was refactored so that a subclass could define it&rsquo;s own
153+
<code>build_parser</code> method which would build a completely different parser. In
154+
other words, one could use the basic machinery in the markdown library to
154155
build a parser of a different markup language without the overhead of building
155156
the markdown parser and throwing it away.</p>
156-
<p>Import statements within markdown have been improved so that third party
157+
<p>Import statements within markdown have been improved so that third party
157158
libraries can embed the markdown library if they desire (licensing permitting).</p>
158-
<p>Added support for Python&rsquo;s <code>-m</code> command line option. You can run the markdown
159-
package as a command line script. Do <code>python -m markdown [options] [args]</code>.
160-
Note that this is only fully supported in Python 2.7+. Python 2.5 &amp; 2.6
159+
<p>Added support for Python&rsquo;s <code>-m</code> command line option. You can run the markdown
160+
package as a command line script. Do <code>python -m markdown [options] [args]</code>.
161+
Note that this is only fully supported in Python 2.7+. Python 2.5 &amp; 2.6
161162
require you to call the module directly (<code>markdown.__main__</code>) rather than
162163
the package (<code>markdown</code>). This does not work in Python 2.4.</p>
163-
<p>The command line script has been renamed to <code>markdown_py</code> which avoids all the
164-
various problems we had with previous names. Also improved the command line
164+
<p>The command line script has been renamed to <code>markdown_py</code> which avoids all the
165+
various problems we had with previous names. Also improved the command line
165166
script to accept input on <code>stdin</code>.</p>
166-
<p>The testing framework has been completely rebuilt using the Nose testing
167+
<p>The testing framework has been completely rebuilt using the Nose testing
167168
framework. This provides a number of benefits including the ability to better
168-
test the built-in extensions and other options available to change the parsing
169+
test the built-in extensions and other options available to change the parsing
169170
behavior. See the <a href="../../test_suite/">Test Suite</a> documentation for details.</p>
170-
<p>Various bug fixes have been made, which are too numerous to list here. See the
171-
<a href="https://github.com/Python-Markdown/markdown/commits/master">commit log</a> for a
171+
<p>Various bug fixes have been made, which are too numerous to list here. See the
172+
<a href="https://github.com/Python-Markdown/markdown/commits/master">commit log</a> for a
172173
complete history of the changes.</p>
173174

174175
</div>
@@ -277,7 +278,7 @@ <h3>Navigation</h3>
277278

278279
<!--
279280
MkDocs version : 0.17.2
280-
Docs Build Date UTC : 2017-12-06 21:11:41
281+
Docs Build Date UTC : 2017-12-06 23:52:12
281282
-->
282283
</body>
283284
</html>

change_log/release-2.2/index.html

100755100644
+17-17
Original file line numberDiff line numberDiff line change
@@ -67,24 +67,24 @@ <h3>Navigation</h3>
6767
<div class="documentwrapper">
6868
<div class="bodywrapper">
6969
<div class="body" role="main"><h1 id="python-markdown-22-release-notes">Python-Markdown 2.2 Release Notes<a class="headerlink" href="#python-markdown-22-release-notes" title="Permanent link">&para;</a></h1>
70-
<p>We are pleased to release Python-Markdown 2.2 which makes improvements on 2.1.
71-
While 2.2 is primarily a bug fix release, some internal improvements were made
70+
<p>We are pleased to release Python-Markdown 2.2 which makes improvements on 2.1.
71+
While 2.2 is primarily a bug fix release, some internal improvements were made
7272
to the parser, and a few security issues were resolved.</p>
73-
<p>Python-Markdown supports Python versions 2.5, 2.6, 2.7, 3.1, and 3.2 out
74-
of the box. </p>
73+
<p>Python-Markdown supports Python versions 2.5, 2.6, 2.7, 3.1, and 3.2 out
74+
of the box.</p>
7575
<h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="headerlink" href="#backwards-incompatible-changes" title="Permanent link">&para;</a></h2>
7676
<p>While Python-Markdown has received only minor internal changes since the last
7777
release, there are a few backward-incompatible changes to note:</p>
7878
<ul>
7979
<li>
80-
<p>Support had been dropped for Python 2.4. No guarantees are made that the
81-
library will work in any version of Python lower than 2.5. Additionally, while
82-
the library had been tested with Python 2.5, consider Python 2.5 support to be
80+
<p>Support had been dropped for Python 2.4. No guarantees are made that the
81+
library will work in any version of Python lower than 2.5. Additionally, while
82+
the library had been tested with Python 2.5, consider Python 2.5 support to be
8383
depreciated. It is not likely that any future versions will continue to support
8484
any version of Python less than 2.6.</p>
8585
</li>
8686
<li>
87-
<p>For many years Python-Markdown has identified <code>&lt;ins&gt;</code> and <code>&lt;del&gt;</code> tags in
87+
<p>For many years Python-Markdown has identified <code>&lt;ins&gt;</code> and <code>&lt;del&gt;</code> tags in
8888
raw HTML input as block level tags. As they are actually inline level tags,
8989
this behavior has been changed. This may result in slightly different output.
9090
While in most cases, the new output is more correct, there may be a few edge
@@ -93,19 +93,19 @@ <h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="
9393
</li>
9494
<li>
9595
<p>The behavior of the <code>enable_attributes</code> keyword has been slightly altered.
96-
If authors have been using attributes in documents with <code>safe_mode</code> on, those
96+
If authors have been using attributes in documents with <code>safe_mode</code> on, those
9797
attributes will no longer be parsed unless <code>enable_attributes</code> is explicitly
9898
set to <code>True</code>. This change was made to prevent untrusted authors from injecting
99-
potentially harmful JavaScript in documents. This change had no effect when
99+
potentially harmful JavaScript in documents. This change had no effect when
100100
not in <code>safe_mode</code>.</p>
101101
</li>
102102
</ul>
103103
<h2 id="whats-new-in-python-markdown-22">What&rsquo;s New in Python-Markdown 2.2<a class="headerlink" href="#whats-new-in-python-markdown-22" title="Permanent link">&para;</a></h2>
104-
<p>The docs were refactored and can now be found at
104+
<p>The docs were refactored and can now be found at
105105
<a href="http://packages.python.org/Markdown/">http://packages.python.org/Markdown/</a>. The docs are now maintained in the
106106
Repository and are generated by the <code>setup.py build_docs</code> command.</p>
107-
<p>The Sane_Lists
108-
extension was added. The Sane Lists Extension alters the behavior of the
107+
<p>The <a href="../../extensions/sane_lists/">Sane_Lists</a>
108+
extension was added. The Sane Lists Extension alters the behavior of the
109109
Markdown List syntax to be less surprising by not allowing the mixing of list
110110
types. In other words, an ordered list will not continue when an unordered list
111111
item is encountered and vice versa.</p>
@@ -115,10 +115,10 @@ <h2 id="whats-new-in-python-markdown-22">What&rsquo;s New in Python-Markdown 2.2
115115
As long as the provided module contains a compatible extension, the extension
116116
will be loaded.</p>
117117
<p>The BlockParser API was slightly altered to allow <code>blockprocessor.run</code> to return
118-
<code>True</code> or <code>False</code> which provides more control to the block processor loop from
118+
<code>True</code> or <code>False</code> which provides more control to the block processor loop from
119119
within any Blockprocessor instance.</p>
120-
<p>Various bug fixes have been made. See the
121-
<a href="https://github.com/Python-Markdown/markdown/commits/master">commit log</a>
120+
<p>Various bug fixes have been made. See the
121+
<a href="https://github.com/Python-Markdown/markdown/commits/master">commit log</a>
122122
for a complete history of the changes.</p>
123123

124124
</div>
@@ -227,7 +227,7 @@ <h3>Navigation</h3>
227227

228228
<!--
229229
MkDocs version : 0.17.2
230-
Docs Build Date UTC : 2017-12-06 21:11:41
230+
Docs Build Date UTC : 2017-12-06 23:52:12
231231
-->
232232
</body>
233233
</html>

0 commit comments

Comments
 (0)