aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Some fixes requested by @waylan, cleanup and tests improvementsDmitry Shachnev2013-07-273-13/+20
|
* Use smarty extension when building docsDmitry Shachnev2013-07-261-1/+1
|
* Add documentation for smarty extensionDmitry Shachnev2013-07-265-4/+63
|
* Add smarty extension, based on SmartyPants libraryDmitry Shachnev2013-07-264-0/+273
|
* Added support for attr_lists on definition list terms.Waylan Limberg2013-07-194-4/+24
| | | | | | | | Like headers (h1-6) dt's can only be on one line, so we need to use the header regex on dt's. This was implemented after considering a recent [discussion](http://six.pairlist.net/pipermail/markdown-discuss/2013-July/002859.html) on the markdown mailing list. Prior to that discussion, I never considered that it was impossable to set block level attrs on dt's. Now it is.
* Allow inline attr_lists at end of header.Waylan Limberg2013-07-193-3/+3
| | | | | | | | | | A header can be only one line - so unlike other block level elements, a attr_list must be at th eend of the line. To disingush it from an inline attr_list on the last child in a header, we must require at least one space before th eblock-level attrt_list. Always intended it to work that way. Not sure how I missed that before. At least we're testing for it now.
* Attr_List Extension now also supports nested ol's.Waylan Limberg2013-07-193-12/+54
| | | | | | | | | | Not sure how I missed that when committing ea4af0d. Also as a side-effect, this fixes #230 - which brought my previous oversight to my attention. Thanks for the report @divisoryang. Also added some tests - including tests of list items without attr_lists. Sometimes I forget to test markup that does not use an extension when an extension is enabled. That's what resulted in #230 being reported.
* MetaData no longer fails with no newline. Fixes #228.Waylan Limberg2013-07-032-1/+8
|
* Minor cleanup.Waylan Limberg2013-06-161-1/+0
|
* Attr_List Extension now support attr_lists on nested lists.Waylan Limberg2013-06-163-2/+51
| | | | | | A list item with a nested list complicates were the attr_list can be. Fixes #218. Thanks for the report @jpzimmer.
* Fixed wikilinks extension's handling of config setting. Not sure how I ↵Waylan Limberg2013-06-161-2/+2
| | | | didn't notice the tests were failing for this before.
* Improved codehilite docs. Document `css_class` setting.Waylan Limberg2013-06-161-5/+13
| | | | | | Also cleaned up poor wording on other setting for codehilite. Thanks for the inital suggestion @davidcorne. Fixes #223.
* AbbrExtension now handles abbreviations nested in other markup.Waylan Limberg2013-06-162-2/+11
| | | | | | | | Just set each abreviation as an AtomicString. Given the nature of abbreviations, they are not likely to ever contain any other markup anyway. Also added a test. Fixes #224. Thanks for the report @JakeChampion.
* Fixed #216. WikiLink Extension actually accepts configs.Waylan Limberg2013-05-191-2/+2
|
* Updated extension API docs to list output_format and serializer on the md ↵Waylan Limberg2013-05-091-6/+9
| | | | | | | | | instance. I still need to document everything on that list and probably a few things missing from the list. I also updated the warning about monkey patching to be a "Warning" admonition - now that we have that extension. Probably should depreciate access to md_globals in the extension API -- as we don't actually use any anymore. That dates back to pre-OO code.
* Merge pull request #212 from shvechikov/patch-1Waylan Limberg2013-04-151-1/+1
|\ | | | | Fixed a typo in the docs
| * Fixed a typo in the docsLeonid Shvechikov2013-04-151-1/+1
|/
* Merge pull request #207 from mitya57/cleanupWaylan Limberg2013-03-234-11/+4
|\ | | | | Some minor code cleanups
| * odict.py: remove usage of iteritems_compat which was not workingDmitry Shachnev2013-03-231-8/+3
| | | | | | | | | | | | | | | | | | I've added iteritems_compat function in one of my previous pull requests, which was failing with: ./markdown/odict.py:106: undefined name 'iteritems_compat' This commit drops usage of that function.
| * Remove some unused importsDmitry Shachnev2013-03-233-3/+1
|/
* Version 2.3.12.3.1.finalWaylan Limberg2013-03-221-1/+1
|
* Added a note about tox in test suite docs.Waylan Limberg2013-03-191-1/+7
|
* 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
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-04 23:55:48 +0000