aboutsummaryrefslogtreecommitdiffstats
path: root/markdown/extensions/meta.py
Commit message (Collapse)AuthorAgeFilesLines
* Run Meta after whitespace normalizationWaylan Limberg2014-09-261-1/+1
| | | | Fixes #343. Thanks for the report @AlexJF.
* Standardized all extension header comments to a uniform format.Waylan Limberg2014-08-211-32/+8
|
* 'http://packages.python.org/Markdown/' => ↵Waylan Limberg2014-08-211-1/+1
| | | | 'https://pythonhosted.org/Markdown/'. The former redirects to the latter anyway. Might as well point to the actual destination.
* Update extensions for Extension.__init__ refactorWaylan Limberg2014-07-311-2/+3
| | | | | | | | | | | | | | | | | Fixes #325. All extensions can now accept a dict of configs or **kwargs, not just a list of tuples. Third party extensions may want to follow suite. Extensions may only accept keyword arguments in the future. These changes still need to be documented. A couple things of note: The CodeHilite extension previously issued a DeprecationWarning if the old config key `force_linenos` was used. With thins change, a KeyError will now be raised. The `markdown.util.parseBoolValue` function gained a new argument: `preserve_none` (defaults to False), which when set to True, will pass None through unaltered (will not convert it to False).
* Make doctests support Python 3Dmitry Shachnev2014-06-111-4/+4
|
* MetaData no longer fails with no newline. Fixes #228.Waylan Limberg2013-07-031-1/+1
|
* Future imports go after the docstringsAdam Dinwoodie2013-03-181-1/+1
| | | | | | | | | 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.Waylan Limberg2013-02-271-10/+7
| | | | | | | | | | 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.
* Fixed #106. Replaced all references to freewisdom.org (except for Yuri's ↵Waylan Limberg2012-06-281-2/+2
| | | | homepage).
* Added doctests to fabfile and edited them to pass in all supported versions ↵Waylan Limberg2011-08-021-5/+6
| | | | of python. Note: one test (meta) is still failing on Python 3 due to unicode strings.
* Added an alternative meta list syntax.David Chambers2011-02-171-1/+5
| | | | | | | | | | | | | | | Implicit syntax (existing): tag: Python Markdown Explicit syntax (new): tag: Python tag: Markdown These two examples are now equivalent. Previously, the latter would produce `{u'tag': [u'Markdown']}` rather than `{u'tag': [u'Python', u'Markdown']}`.
* Break cyclic import of markdown. This allows people to embed markdownToshio Kuratomi2010-07-051-1/+2
| | | | if they desire.
* Updated meta extension for new refactor.Waylan Limberg2008-11-201-1/+1
|
* Moved markdown_extensions/ to markdown/extensions. Markdown is now one ↵Waylan Limberg2008-11-201-0/+90
package instead of two.