aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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
| |
| * Fix typo in release-2.6.txtnikolas2015-01-281-1/+1
|/
* Add offical support for PyPy.Waylan Limberg2015-01-103-2/+8
|
* Added test-requirements.txtWaylan Limberg2015-01-102-4/+5
| | | | This should make it easier to install test deps even when not using tox.
* Clean up a few typos and formatting issues.Waylan Limberg2015-01-012-55/+51
|
* More refactor of TOC Extension.Waylan Limberg2015-01-011-24/+24
| | | | | | Mostly just code cleanup so it reads better. Renamed a few internal things. I didn't write this extension originally so most of this would have been done a long time ago. I just havn't touched this code much till now.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2015-01-011-1/+1
|\
| * Merge pull request #381 from svetlyak40wt/patch-1Waylan Limberg2014-12-311-1/+1
| |\ | | | | | | Fix a small typo
| | * Fix a small typoAlexander Artemenko2014-12-311-1/+1
| |/
* / HeaderId Extension marked as Pending Deprecation.Waylan Limberg2015-01-016-157/+289
|/ | | | | | | | | | | | | | | | | | | | Use the Table of Contents Extension instead. The HeaderId Extension will raise a PendingDeprecationWarning. The last few features of the HeaderID extension were mirgrated to TOC including the baselevel and separator config options. Also, the marker config option of TOC can be set to an empty string to disable searching for a marker. The `slugify`, `unique` and `stashedHTML2text` functions are now defined in the TOC extension in preperation for the HeaderId extension being removed. All coresponding tests are now run against the TOC Extension. The meta-data support of the HeaderId Extension was not migrated and no plan exists to make that migration. The `forceid` config option makes no sense in the TOC Extension and the only other config setting supported by meta-data was the `header_level`. However, as that depends on the template, it makes more sense to not be defined at the document level.
* Added first draft of 2.6 release notes.Waylan Limberg2014-12-305-6/+142
|
* PendingDeprecationWarning (v2.5) => DeprecationWarning (v2.6)Waylan Limberg2014-12-303-41/+35
|
* Preserve order of nested headers in TOCWaylan Limberg2014-12-304-49/+108
| | | | | | | | | Fixes #380. The TOC replacement is now seperate from building the TOC, which allows us to iter through the doc in order rather than with the non-order-preserving interparent pethod. This is almost a complete refactor of the run method. Also cleaned up the config stuff. Thanks to @colewerner for the report and test case.
* Merge branch 'temp'Waylan Limberg2014-12-302-14/+54
|\ | | | | | | | | Conflicts: tests/test_extensions.py
| * Complete test coverage of TOC ExtensionWaylan Limberg2014-12-302-8/+48
| |
| * Always add toc to Markdown Class InstanceWaylan Limberg2014-12-301-6/+6
| | | | | | | | | | | | | | | | Previously, we only added the toc attribute (md.toc) if no Marker was found within the document. However, that has caused framworks to do things like force insert a marker, run convert, then extract the toc from the body of the document. This is much cleaner. And if the user wants to add the toc to the document also, they still can.
| * Add reset support to TOC extension.Waylan Limberg2014-12-302-0/+14
| | | | | | | | | | | | Now, whenever the TOC extensiuon is loaded, the Markdown class instance will always have a toc attribute (md.toc). Calling md.reset() will also reset the toc attribute which defaults to an empty string.
* | Fix testWaylan Limberg2014-12-301-12/+1
| |
* | Add reset support to TOC extension.Waylan Limberg2014-12-302-0/+25
|/ | | | | | Now, whenever the TOC extensiuon is loaded, the Markdown class instance will always have a toc attribute (md.toc). Calling md.reset() will also reset the toc attribute which defaults to an empty string.
* Better docs of treeprocessor API.Waylan Limberg2014-12-291-3/+14
| | | Fixes #375. Explains the difference between returning None and returning a modified root element. Also makes the docs more consistent with the doc strings in the code.
* Merge pull request #378 from d0ugal/docs-fixWaylan Limberg2014-12-231-4/+5
|\ | | | | Correct the documentation for the slugify function
| * Correct the documentation for the slugify functionDougal Matthews2014-12-221-4/+5
| | | | | | | | | | The previous requirements are incorrect, the method needs to accept two parameters.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-25 08:01:25 +0000