aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Ensure handleAttributes doesn't lose AtomicStrings.Waylan Limberg2013-03-181-3/+3
| | | | | | | | | | | | | | | Fixes #204. This was a real pain to debug. But I think the problem stemmed from the fact that the footnote extension inserted a etree link into the footnotes last p element. Then when inline patterns are run, the inline code in that p element is processed. Normally, code would be the first child found, but with the pre-existing link, that wasn't the case and the parser took a slightly differant path which would never be encountered in any other situation. It was this slightly differant path that made the lose of the AtomicString status of the inline code matter. Since any AtomicString (including inline code) doesn't need to be run though hanldeAttributes anyway, we can just skip over it and preserve the AtomicString. Whew!
* Merge pull request #205 from Gamma3000/future-orderWaylan Limberg2013-03-1823-33/+36
|\ | | | | Future statement ordering
| * Use lead blockprocessor comment as docstringAdam Dinwoodie2013-03-181-10/+12
| | | | | | | | | | | | The lead comment in blockprocessors.py should really be a docstring for consistency with other files. Fix this with the other part of @Arfrever's patch for issue #203.
| * Future imports go after the docstringsAdam Dinwoodie2013-03-1823-23/+24
|/ | | | | | | | | 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.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2013-03-152-4/+11
|\
| * Merge pull request #201 from mitya57/pyflakes-fixesWaylan Limberg2013-03-152-4/+11
| |\ | | | | | | Fix some pyflakes-undefined-name warnings
| | * Fix some pyflakes-undefined-name warningsDmitry Shachnev2013-03-152-4/+11
| |/
* / More makefile cleanup. Fixes #202.Waylan Limberg2013-03-152-3/+11
|/
* Allow run-tests script options and args to be passed through to nose.Waylan Limberg2013-03-151-6/+4
|
* Merge pull request #200 from timonwong/masterWaylan Limberg2013-03-151-1/+1
|\ | | | | Fix wrong 'linenos' argument for CodeHilite(), in fenced_code.py
| * Update fenced_code.pyTimon Wong2013-03-151-1/+1
|/ | | CodeHilite: linenos is replaced by linenums
* Date release 2.3 in change_logWaylan Limberg2013-03-151-1/+1
|
* Fixed a few minor issues with the makefile discovered deploying the last ↵Waylan Limberg2013-03-151-4/+7
| | | | release.
* Version 2.3 Final2.3.finalWaylan Limberg2013-03-141-1/+1
|
* Added PyTidyLib to tox deps and set download-cache.Waylan Limberg2013-03-141-1/+3
|
* Updated testing framework to use PyTidyLib rather than uTidyLib for Python 3 ↵Waylan Limberg2013-03-132-27/+26
| | | | support.
* Removed html_tidy docs.Waylan Limberg2013-03-131-34/+0
|
* Removed the html_tidy extension. See 2.3 release notes for explaination.Waylan Limberg2013-03-136-82/+22
|
* Added Python 3.3 to list of supported versions and removed 2.5.Waylan Limberg2013-03-061-1/+1
|
* Switched testing to tox.Waylan Limberg2013-03-015-106/+62
| | | | | | | | | | Also scrapped fabfile.py and replaced it with a much simpler makefile. Tox does most of the stuff that was in fabfile.py anyway. Now that everything runs in all supported python versions without using 2to3, we don't need to wait for tox to support it.
* Tweaked the docs some more.Waylan Limberg2013-02-276-56/+72
|
* Minor formatting edit to release notes for v2.3.Waylan Limberg2013-02-271-1/+1
|
* Updated release notes for v2.3. to reflect recent changes.Waylan Limberg2013-02-271-14/+32
|
* Dict.keys() does not return a list in Python 3.Waylan Limberg2013-02-272-2/+2
|
* Merge branch '2and3'Waylan Limberg2013-02-2731-304/+324
|\
| * Now using universal code for Python 2 & 3.Waylan Limberg2013-02-2730-271/+311
| | | | | | | | | | | | | | | | | | | | 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.
| * Simlify importing ElementTreeWaylan Limberg2013-02-262-33/+13
| | | | | | | | | | | | As we no longer support older python versions, importing ElementTree is much simpler. The documented way for extensions to use etree still remains the same.
* | CodeHilite tests pass in all pygments versions.Waylan Limberg2013-02-251-15/+11
| |
* | Update tests to only run on supported versions of python.Waylan Limberg2013-02-251-1/+1
| |
* | Missed a set.append -> set.add.Waylan Limberg2013-02-251-1/+1
| |
* | Consistant parsing of attr_lists in Python3.3Waylan Limberg2013-02-251-2/+2
|/ | | | | | Fixes #194. The NAME_RE regex was failing in Python 3.3 with the range `\u10000-\ueffff`. Also, in Python =< 3.2 the range `\u0300-\u036f` matches a colon but not in Python 3.3.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2013-02-221-4/+6
|\
| * Better clarify the 4 space indentation rule.Waylan Limberg2013-02-211-7/+5
| | | | | | A better explanation for #193 that includes all block-level elements nested in lists.
| * Update docs/index.txtWaylan Limberg2013-02-211-0/+4
| | | | | | | | | | | | Clarify that strict 4 space indentation applies to nested lists.  Closes #193. Hopefully, people will read this in the docs before filing bug reports in the future. One can dream.
* | Change `set.append` -> `set.add` in `headerid.unique`Waylan Limberg2013-02-223-3/+10
|/ | | | | | | | | Fixes #195. This was getting missed because the HeadrerId extension's reset method was resetting the IDs to a list. However, some third party extensions may want to call the unique function and it should work as documented. Interestingly, the TOC extension was using it and passing in a list as well. All fixed now. Also added a test of the `unique` function directly so we shouldn't repeat this in the future.
* Various changes to docs for updated changes, clarity, and to fix typos.Waylan Limberg2013-02-1913-160/+171
|
* Updated toc tests.Waylan Limberg2013-02-192-2/+2
|
* More TOC cleanup and added tests.Waylan Limberg2013-02-191-2/+2
|
* TOC list item names must use text from all children.Waylan Limberg2013-02-191-1/+1
|
* Updated toc extension to work with changes @ 4ff74e3.Waylan Limberg2013-02-191-2/+2
|
* Ensure toc attribute is available on Markdown class.Waylan Limberg2013-02-193-5/+61
| | | | | | This appears to have recently been broken with the fixes in #191. This time I've added tests to prevent future breakage and added documentation to explain the behavior.
* Merge pull request #192 from benjaoming/masterWaylan Limberg2013-02-184-28/+45
|\ | | | | Little changes
| * adding test for out of order headlinesbenjaoming2013-02-183-0/+16
| |
| * Do not use assigned names "next" and "id", rename to order_toc_list and ↵benjaoming2013-02-181-18/+20
| | | | | | | | clean up code
| * Merge branch 'toc-fix'benjaoming2013-02-181-13/+12
|/|
| * code cleanupbenjaoming2013-02-181-13/+12
| |
* | Merge pull request #191 from benjaoming/toc-fixWaylan Limberg2013-02-171-63/+126
|\| | | | | Make TocTreeprocessor extendable and be gentle on badly structured headings
| * Make TocTreeprocessor extendable and be more gentle on badly structured headingsbenjaoming2013-02-171-63/+126
|/
* Allow better linenum override in CodeHiliteWaylan Limberg2013-02-144-20/+125
| | | | | | | | | | | Fixes #148. The "force_linenos" config setting of the CodeHilite extension has been marked as Pending Deprecation and a new setting "linenums" has been added to replace it. See documentation for the [CodeHilite Extension] for an explaination of the new "linenums" setting. The new setting will honor the old "force_linenos" if it is set, but it will raise a PendingDeprecationWarning and will likely be removed in a future version of Python-Markdown. [CodeHilite Extension]: extensions/codehilite.html
* Preserve all blank lines in code blocks.Waylan Limberg2013-02-142-14/+14
| | | | | | | | | | | | Fixes #183. Finally got this working properly. The key was using a regex substitution with non-overlapping matches that removed all whitespace from the begining of *all* blank lines when normalizing whitespace. Once I got that, I could simplfy the EmptyBlockProcessor and easily output one or two blank lines appropriately. A blank block gets two new lines (`'\n\n'`), while a block which starts with a newline gets one.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 11:05:43 +0000