From d824986c14eb9f6bbe49a79382e1cddd4a32c0d2 Mon Sep 17 00:00:00 2001 From: Adam Dinwoodie Date: Mon, 18 Mar 2013 20:54:14 +0000 Subject: Future imports go after the docstrings 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. --- markdown/extensions/__init__.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'markdown/extensions/__init__.py') diff --git a/markdown/extensions/__init__.py b/markdown/extensions/__init__.py index 960d8f9..184c4d1 100644 --- a/markdown/extensions/__init__.py +++ b/markdown/extensions/__init__.py @@ -1,9 +1,10 @@ -from __future__ import unicode_literals """ Extensions ----------------------------------------------------------------------------- """ +from __future__ import unicode_literals + class Extension(object): """ Base class for extensions to subclass. """ def __init__(self, configs = {}): -- cgit v1.2.3