aboutsummaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Fixed an old typo in the smarty extension and added a test case.Martin Altmayer2014-08-112-1/+3
|
* Fixed silly typo. Relates to #325.Waylan Limberg2014-08-011-1/+1
|
* Ensure Extension.getConfigInfo Test always passesWaylan Limberg2014-08-011-2/+3
| | | | | Dicts don't preserve order but still will be equal while lists of tuples always preserve order. When we use a dict to create a list of tuples, the results are unpredictable - especially for a equality test. so we need to compare dicts, not lists. Related to #325
* Update extensions for Extension.__init__ refactorWaylan Limberg2014-07-311-16/+21
| | | | | | | | | | | | | | | | | 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).
* Refactor markdown.extensions.Extension.__init__()Waylan Limberg2014-07-291-1/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As pointed out in #325, setting up Extension configs is kind of a mess. Some places pass a list of tuples on initialization, others a dict. And sometimes they're passed as an arg, othertimes a kwarg. Addiitonaly, the docs are just as inconsistant. This refactor addresses all those sinerios with tests included. The existing extensions still need refactored. But the fact that their tests still pass means we havn't broken third party extensions either. This refactor also introduces a new API, which is the prefered method going forward. All docs should be updated to match. Whereas previously one might do: ```python MyExtension(configs={'key': 'foo', 'otherkey': 'bar'}) ``` This can now be done: ```python MyExtension(key='foo', otherkey='bar') ``` Of course, the old way still works for backward compatability. But that means the `configs` keyword has special status and cannot be used for another purpose.
* Add tests of markdown.extensions.ExtensionWaylan Limberg2014-07-111-0/+23
|
* 100% test coverage of admonitionsWaylan Limberg2014-07-102-0/+2
|
* smarty: add support for angled quotesDmitry Shachnev2014-06-193-1/+6
| | | | See <http://en.wikipedia.org/wiki/Guillemet>.
* Add failing unit test for smarty: ellipsis before close double quote ↵Lawrence Kesteloot2014-05-312-0/+3
| | | | generates opening double quote.
* Merge pull request #311 from mitya57/masterWaylan Limberg2014-05-261-1/+1
|\ | | | | Make smarty extension work together with attr_list
| * Add smarty to extensions for attr_list testDmitry Shachnev2014-05-061-1/+1
| | | | | | | | To make it easier to notice (and fix) the failure.
* | Fix issue308 and fix (unrelated) failure to break out of nest loop.ryneeverett2014-05-212-1/+14
|/
* Skip a weird PHP test.Waylan Limberg2014-04-201-0/+4
| | | I can't make out what this PHP test is trying to accomplish. From my point of view, our output is fine. So we skip this test.
* No assertIs in Python 2.6. Fixes #294Waylan Limberg2014-04-201-1/+1
|
* Add a (failing) test for Smarty extension.Dmitry Shachnev2014-02-132-1/+3
|
* Fix some tests failuresDmitry Shachnev2014-02-121-1/+1
|
* Merge branch 'master' of github.com:waylan/Python-MarkdownWaylan Limberg2014-01-123-0/+25
|\
| * Merge pull request #267 from ryneeverett/attr_list-tablesWaylan Limberg2014-01-113-0/+25
| |\ | | | | | | tables and attr_list compatibility
| | * tables_and_attr_list testryneeverett2014-01-113-0/+25
| | |
* | | Improved multiline comment parsing.Waylan Limberg2014-01-124-8/+52
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #257 and slightly alters comment parsing behavior. Unlike self-closing tags, a comment can contain angle brackets between the opening and closing tags. The greaterthan angle bracket at the end of the first block should not be mistaken for closing the comment. Need to actually check for a comment closing tag (`-->`). If one if not found, then the comment keeps going (to the end of the document if nessecary) just like in HTML. That last bit is a slight change from previous behavior, but should be unsurprising as that's how broswers parse html comments. And as far as I can tell, more implementations follow this behavior than any other. The ones that don't seem to be all over the place.
* | No longer percent encode spaces in urls.Waylan Limberg2014-01-092-3/+3
| | | | | | | | | | | | | | | | | | | | | | The current implementation was wrong as it also percent encoded query strings (which should be plus encoded) and calling urllib.quote on the path (and urllib.quote_plus on the query string) assumes the url is not already encoded. What if the document author pasted a url that was already encoded? She probably did not intend for `%20` to become `%2520`. Or did she? It is now clear to me why many implementation do nothing to urls. Just pass them though as-is. To bad if they are not valid HTML. HTML authors have to encodee their own urls, so I guess markdown authors have to as well.
* | Only escape ESCAPED_CHARS.Waylan Limberg2014-01-092-0/+24
| | | | | | | | | | | | Leave all other chars prefaced by a backslash alone. Fixes #242. Not sure why I thought that I needed to add another backslash. Thanks for the report and the test case @mhubig.
* | Address various depreciated APIs in PythonWaylan Limberg2014-01-081-4/+4
| | | | | | | | | | This mostly revolves around old APIs for ElementTree, but includes a few others as well. Fixes #254. Thanks for the report.
* | Merge pull request #274 from ajdavis/highlight-linesWaylan Limberg2014-01-071-0/+84
|\ \ | | | | | | Add feature for emphasizing some lines in a code block.
| * | Allow single as well as double quotes for hl_lines.A. Jesse Jiryu Davis2014-01-071-15/+19
| | |
| * | Support syntax for highlighted lines like: ```python hl_lines=“1 3”A. Jesse Jiryu Davis2014-01-061-2/+35
| | |
| * | Add feature for emphasizing some lines in a code block.A. Jesse Jiryu Davis2014-01-031-0/+47
| |/ | | | | | | A code blocked headed by “:::python{1,3}” now emphasizes the first and third lines. With fences enabled, ```python{1,3} has the same effect.
* / Fixed parsing of brackets within inline image titles.Darell Tan2014-01-052-0/+21
|/
* Issue #52ryneeverett2013-10-142-6/+57
|
* toc: insert `&para;` instead of raw unicode characterDmitry Shachnev2013-09-291-4/+4
|
* Add tests for the previous two commitsDmitry Shachnev2013-09-254-10/+23
|
* Ensure each term on def list maintains its own loose status.Waylan Limberg2013-09-022-1/+22
| | | | | | Previously, the code was ignoring whether this was a new term when determining whether the currect item should be loose or not. Fixes #243. Thanks for the report @Anomareh.
* Allow extensions to register serializersWaylan Limberg2013-08-071-0/+18
| | | | | | | | | Setting output_format must happen after extensions are loaded. Only in that way can an extension register a serializer so that it will then be available to be used with the output_format keyword. A test has been added to avoid this regression from happening again in the future. Fixes #238, partially reverses commit 41cc055 and provides a better fix for
* Serializers now preserve case of tags.Waylan Limberg2013-08-071-0/+32
| | | | | | | It is up to the markdown code (and extension authors to make sure tags are of the correct case (there may be cases were an extension might need to mix cases - which should be preserved). Fixes #237. Thanks for the report @eichin.
* HeaderID Ext now handles raw html in ids. Fixes #232Waylan Limberg2013-07-281-0/+12
|
* Some fixes requested by @waylan, cleanup and tests improvementsDmitry Shachnev2013-07-272-2/+11
|
* Add smarty extension, based on SmartyPants libraryDmitry Shachnev2013-07-263-0/+38
|
* Added support for attr_lists on definition list terms.Waylan Limberg2013-07-193-2/+22
| | | | | | | | 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-192-2/+2
| | | | | | | | | | 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-192-1/+43
| | | | | | | | | | 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-031-0/+7
|
* Attr_List Extension now support attr_lists on nested lists.Waylan Limberg2013-06-162-1/+23
| | | | | | A list item with a nested list complicates were the attr_list can be. Fixes #218. Thanks for the report @jpzimmer.
* AbbrExtension now handles abbreviations nested in other markup.Waylan Limberg2013-06-161-0/+9
| | | | | | | | 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.
* Remove some unused importsDmitry Shachnev2013-03-231-1/+0
|
* Updated testing framework to use PyTidyLib rather than uTidyLib for Python 3 ↵Waylan Limberg2013-03-131-21/+20
| | | | support.
* CodeHilite tests pass in all pygments versions.Waylan Limberg2013-02-251-15/+11
|
* Change `set.append` -> `set.add` in `headerid.unique`Waylan Limberg2013-02-221-0/+7
| | | | | | | | | 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.
* Updated toc tests.Waylan Limberg2013-02-192-2/+2
|
* Ensure toc attribute is available on Markdown class.Waylan Limberg2013-02-191-0/+39
| | | | | | 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.
* adding test for out of order headlinesbenjaoming2013-02-183-0/+16
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-25 13:43:59 +0000