aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Coverage 4.0 dropped support for Python 3.2. Until we drop Python 3.2, we ↵Waylan Limberg2015-10-261-1/+1
| | | | must stick with coverage<4.0.
* Merge pull request #432 from facelessuser/masterWaylan Limberg2015-09-053-4/+16
|\ | | | | Fix infinite loop #430
| * Fix infinite loop #430facelessuser2015-09-043-4/+16
|/ | | | | | | | | This should fix the remaining corner cases that can cause infinite loops. Previous iterations did not account for scenarios where the “end” index was less than the “start” index. If the “end” index is ever less than or equal to the “start” index, the “end” will be adjusted to to be “start” + 1 allow the full range to be extracted and replaced.
* Merge pull request #429 from Tigge/patch-1Waylan Limberg2015-08-293-1/+21
|\ | | | | Fix find footnote placeholder to recurse
| * Fix find footnote placeholder to recurseGustav Tiger2015-08-293-1/+21
|/
* Merge pull request #419 from mitya57/masterWaylan Limberg2015-06-205-12/+16
|\ | | | | Use a different approach to fix the smarty bug
| * Add a test for duplicate angled quotes without smarty extensionDmitry Shachnev2015-06-202-1/+4
| |
| * Override regex for html inline pattern when smart_angled_quotes is trueDmitry Shachnev2015-06-201-1/+6
| | | | | | | | | | Add a restriction that the closing angled quote should not be duplicate, so that we can use our own pattern for handling duplicate quotes.
| * Add a test to make sure quotes processor does not touch code blocksDmitry Shachnev2015-06-192-2/+2
| |
| * Revert "smarty: Use a separate processor for angled quotes"Dmitry Shachnev2015-06-191-8/+4
| | | | | | | | | | | | | | That commit caused a regression where `<<` and `>>` inside code blocks were wrongly replaced with double quotes. This reverts commit 5029d829c1532f31adc9acbf54d88bb469a69a4f.
* | Restict travis to non-experimental branches.Waylan Limberg2015-06-191-0/+4
|/
* Merge pull request #417 from mitya57/masterWaylan Limberg2015-06-153-4/+10
|\ | | | | Fix processing angle quotes in smarty extension
| * smarty: Use a separate processor for angled quotesDmitry Shachnev2015-06-151-4/+8
| | | | | | | | Run that processor before inline processor to fix the test failure.
| * tests: Add a failing case for `<<Hello>>` to smarty testDmitry Shachnev2015-06-152-0/+2
|/
* Merge pull request #415 from karepker/masterWaylan Limberg2015-06-012-11/+28
|\ | | | | Fixed #414 parser ignoring value of `tab_length`
| * Updated BlockProcessor to new-style class. Changed subclasses to use super().Kar Epker2015-06-012-6/+6
| |
| * Changed formatting of regex strings. Fixed flake8 issues.Kar Epker2015-06-012-19/+10
| |
| * Changed line continuations to satisfy pylint.Kar Epker2015-06-012-14/+19
| |
| * Fixed parser ignoring value of tab_length.Kar Epker2015-06-012-9/+30
|/
* Updated change_log for 2.6.2.Waylan Limberg2015-04-201-0/+2
|
* Upped version to 2.6.22.6.2-finalWaylan Limberg2015-04-201-1/+1
|
* Merge pull request #404 from iKevinY/spelling-fixesWaylan Limberg2015-04-061-6/+6
|\ | | | | Miscellaneous capitalization/spelling fixes
| * Miscellaneous capitalization/spelling fixesKevin Yap2015-04-061-6/+6
| |
* | Merge pull request #400 from pieterprovoost/emptytableWaylan Limberg2015-04-063-3/+15
|\ \ | |/ |/| support empty table
| * updated tables testpieterprovoost2015-04-062-2/+11
| |
| * added support for zero row tablespieterprovoost2015-04-052-2/+5
|/
* smarty: Add back special case for decade abbreviationsDmitry Shachnev2015-03-183-6/+10
| | | | | | | | | | The previous version did not work, and was incorrectly removed as part of 85ad18071d619251. In the new version, use lookbehind search for \w instead of \b, so that it works. Update the tests accordingly. Fixes #399 (except parts that we can't fix). Thanks @gandaro for the report.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2015-03-141-5/+5
|\
| * Merge pull request #397 from gandaro/doc-fail-0Waylan Limberg2015-03-131-5/+5
| |\ | | | | | | fix broken documentation code
| | * fix broken documentation codeJakob Kramer2015-03-131-5/+5
| |/
* / Add Comment support to toc.Waylan Limberg2015-03-141-2/+2
|/ | | | | | A etree can contain Comments, PIs or other Elements which do not have a string for a tag. Must always check that a tag is a string before doing string processing on it. Otherwise, things will crash.
* Upped version to 2.6.12.6.1-finalWaylan Limberg2015-03-082-1/+5
|
* Removed `yaml` option from meta-data extension.Waylan Limberg2015-03-084-74/+16
| | | | | The option was buggy. Rather than try to fix it, it is being removed. This feeture should exist as a seperate extension. Fixes #390.
* No `=` in key or value of attr lists.Waylan Limberg2015-02-243-3/+21
| | | | Fixes #389. Thanks for the report @lazka.
* Fix formatting DeprecationWarning messages.Dmitry Shachnev2015-02-201-2/+2
| | | | | Without the space, Python joins the lines and it produces results like 'Positional arguments are depreacted in MarkdownUse keyword arguments only'.
* Upped version to 2.6 final2.6-finalWaylan Limberg2015-02-192-2/+2
|
* Add 'help' command to makefileWaylan Limberg2015-02-191-0/+14
| | | | | I can never remember the names of the subcommands. A 'help' subcommand is an easy assistant for the future.
* No binary operators at begining of line.Waylan Limberg2015-02-184-17/+14
| | | | | | | Apparently this is a new requirement of flake8. That's the thing about using tox. Every test run reinstalls all dependencies so an updated dependency might instroduce new errors. I could specify a specific version, but I like staying current.
* Cleaned up spelling (again).Waylan Limberg2015-02-182-5/+6
|
* Reformatted Release Notes for 2.6.Waylan Limberg2015-02-181-154/+188
| | | | | | | | | This format (using subheading rather than lists), allows for easy linking to each individual section of the release notes. I think we should sue this format going forward. Also added an additional example to clarify the deprecation of the special treatment of the 'mdx_' prefix for third party extensions.
* Added some words missing from Travis' aspell dict.Waylan Limberg2015-02-071-0/+5
|
* Add Docs spellchecking Test.Waylan Limberg2015-02-074-1/+157
| | | | | | | | | | | | | | | | | | | | | | | | Not sure this is the best way to go, but it works. I'm not crazy about running the spellcheck against the built docs, but aspell has a builtin option to easily ignore everything in `<code>` tags which greatly simplfies things. I looked at Doug Hellmans' sphinxcontrib-spelling package which does something similar for Sphinx. However, as Sphinx uses rST and the rST parser outputs a parse tree, Doug is essentially taking that parse tree and running the spellcheck on the appropriate parts (skipping code, etc.). He did a nice [writeup][5] of his development process if you are interested. As Python-Markdown's parse tree is represented as HTML (through ElementTree) I would have to use HTML anyway. And [PyEnchant][2] doesn't currently have good support for HTML. So I used [aspell][3], with inspiration from the [git-spell-check][4] hook. [1]: http://sphinxcontrib-spelling.readthedocs.org/en/latest/index.html [2]: https://pythonhosted.org/pyenchant/ [3]: http://aspell.net/ [4]: https://github.com/mprpic/git-spell-check [5]: http://doughellmann.com/2011/05/26/creating-a-spelling-checker-for-restructuredtext-documents.html
* Thorough spell check of the docs.Waylan Limberg2015-02-0728-429/+441
|
* Added a 'use_pygments' config option to CodeHilite.Waylan Limberg2015-02-054-8/+43
| | | | | | | | | Fixes #386. I'm doing this against my better judgement. The only reason is that I'm using the HTML format suggested by the HTML5 Spec and will simply not consider any alternate output. If a JavaScript library requires something else, to bad. I don't care. That library should support the format suggested by the spec or I'm not interested in it. If you want something else then you can create your own extension which does whatever you want.
* Upgraded to DeprecationWarning on ext `config` keyword.Waylan Limberg2015-02-052-18/+68
| | | | | | | | | Also checked for `None` so the existing extensions will at least still work. Of course, that code all gets deleted with the next release and things will break if extension authors do not update their code. Hope they test there code with each release and check for warnings. Also added a note to the release notes.
* Fix back-compat import of ext names without dots.Waylan Limberg2015-02-021-1/+1
| | | | | | `makeExtension` is the module level function defined in an extension, not `extendMarkdown`, which is the method you override on the Extension class. Do'h. Thanks for catching this @mitya57.
* Use newer ElementTree API to avoid future breakage.Waylan Limberg2015-01-317-10/+9
|
* Only log warnings from commandline script.Waylan Limberg2015-01-314-21/+30
| | | | | | | | | I need to remember this is a lib first and not configure logging from within the lib. Also, from the script we are now actually displaying deprecation warnings. For some reason I don't understnad deprecation warnings are hidden by default in Python. And who remembers to run Python with the `-Wd` flag every time they upgrade a lib just to make sure there's no new deprecations? Fixes #384.
* Merge pull request #382 from nikolas/patch-1Waylan Limberg2015-01-281-1/+1
|\ | | | | Fix typo in release-2.6.txt
| * typo fixnikolas2015-01-281-1/+1
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 17:45:53 +0000