delta/python-markdown.git/markdown/serializers.py, branch baserock/morph github.com: waylan/Python-Markdown.git Future imports go after the docstrings 2013-03-18T20:54:14+00:00 Adam Dinwoodie adam@dinwoodie.org 2013-03-18T20:54:14+00:00 d824986c14eb9f6bbe49a79382e1cddd4a32c0d2 A `from __future__ import ...` statement must go after any docstrings; since putting them before the docstring means the docstring loses its magic and just becomes a string literal. That then causes a syntax error if there are further future statements after the false docstring. This fixes issue #203, using the patch provided by @Arfrever. 
A `from __future__ import ...` statement must go after any docstrings;
since putting them before the docstring means the docstring loses its
magic and just becomes a string literal.  That then causes a syntax
error if there are further future statements after the false docstring.

This fixes issue #203, using the patch provided by @Arfrever.
Now using universal code for Python 2 & 3. 2013-02-27T14:10:47+00:00 Waylan Limberg waylan@gmail.com 2013-02-27T14:10:47+00:00 579288c5eb684dd09d1ef298929a566f40151205 The most notable changes are the use of unicode_literals and absolute_imports. Actually, absolute_imports was the biggest deal as it gives us relative imports. For the first time extensions import markdown relative to themselves. This allows other packages to embed the markdown lib in a subdir of their project and still be able to use our extensions. 
The most notable changes are the use of unicode_literals
and absolute_imports. Actually, absolute_imports was the
biggest deal as it gives us relative imports. For the first
time extensions import markdown relative to themselves.
This allows other packages to embed the markdown lib in a
subdir of their project and still be able to use our
extensions.
It is spelled 'serializers' not 'searializers'. 2012-01-20T09:39:25+00:00 Waylan Limberg waylan@gmail.com 2012-01-20T09:39:25+00:00 dfec5a1a062718caedc24a99c9f31e9fa4a36d15