| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
capitalized. Thanks for the report.
|
| |
|
|
| |
Thanks to skurfer for report and inital patch.
|
| | |
|
| |
|
|
| |
if they desire.
|
| |
|
|
| |
syntax and is implemented as a blockprocessor. Currently, Markdown doesn't see table elements as block elements, so it doesn't get prettified.
|
| |
|
|
| |
major refactor, but it at least works as documented.
|
| | |
|
|
|
package instead of two.
|
