summaryrefslogtreecommitdiff
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
...
* getiterator to iter (#501)Brandon Chinn2016-09-291-1/+1
|
* Replace `getiterator` function for Python 3.6 Brandon Chinn2016-09-291-2/+2
| | | | | | `getiterator` has been deprecated since Python 2.7, when `iter` was added. Fixes #499.
* Up version to 2.6.72.6.7-finalWaylan Limberg2016-09-231-1/+1
|
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2016-09-233-4/+5
|\
| * Fix table alignment when seperator contains spaces (#489)eph2016-08-151-0/+1
| | | | | | | | | | | | | | | | | | | | * Fix table alignment when seperator contains spaces eg. seperator like "------ | :----- | :----: | -----: | ------" * Update tests for table * Delete the newline at the end of tables.html
| * Fix image titles not following specfacelessuser2016-07-261-1/+1
| | | | | | | | | | Don’t allow spaces in image links. This was also causing an issue where any text following a space was treated as a title. Ref #484.
| * Fix another issue with attribute lists (with multiple ‘=’ signs)Dmitry Shachnev2016-06-131-3/+3
| |
* | Don't allow equal signs in attr_list keys.Waylan Limberg2016-09-231-3/+3
|/ | | | | | This will probably not result in the output intending by the author, but the syntax would be incorrect so the author needs to edit the document anyway. We just need to ensure the parser does not crash here. Fixes #498.
* Attribute lists are not permitted to contain newlines. Fixes #482.Waylan Limberg2016-06-121-1/+1
|
* Convert readthedocs link for their .org -> .io migration for hosted projectsAdam Chainz2016-05-291-1/+1
| | | | | | | | As per [their blog post of the 27th April](https://blog.readthedocs.com/securing-subdomains/) ‘Securing subdomains’: > Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard. Test Plan: Manually visited all the links I’ve modified.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2016-04-111-0/+1
|\
| * Support CodeHilite option use_pygments in fenced_codeMartin Morgenstern2016-04-111-0/+1
| |
* | Remove unnessecary if statement.Waylan Limberg2016-04-111-5/+1
|/ | | | | | The statement will never evaluate False, so its not needed. Also, Unicode is not valid for PY3, so its better to not include it. Fixes #470.
* Upped version to 2.6.6.2.6.6-finalWaylan Limberg2016-03-201-1/+1
|
* toc: Remove children from header element after iteratingDmitry Shachnev2016-03-171-1/+2
| | | | Removing items while iterating can result in wrong behavior. Refs #461.
* Improve RawHtmlProcessor to have linear iso quadratic performanceMaurice van der Pot2016-02-261-7/+10
|
* Upped version to 2.6.5.2.6.5-finalWaylan Limberg2015-11-241-1/+1
|
* Fix handling of characters after backtick in tables.Dmitry Shachnev2015-11-071-1/+1
| | | | Fixes #440. Thanks @jandecaluwe for the bug report.
* Upped to version 2.6.4.2.6.4-finalWaylan Limberg2015-11-061-1/+1
|
* Ensure InlinePatterns don't drop newlines.Waylan Limberg2015-11-061-1/+1
| | | | | | Drppoed the non-greedy quantifier from the end of the inlinePatterns as it served no useful purpose and was actually (in very rare edge cases) causing newlines to be dropped. FIxes #439. Thanks to @munificent for the report.
* Upped to version 2.6.3.2.6.3-finalWaylan Limberg2015-10-261-1/+1
|
* Fixed handling of table cell splitMustafa Haddara2015-10-241-2/+49
|
* Fix infinite loop #430facelessuser2015-09-041-3/+4
| | | | | | | | | 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.
* Fix find footnote placeholder to recurseGustav Tiger2015-08-291-1/+3
|
* 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.
* 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.
* smarty: Use a separate processor for angled quotesDmitry Shachnev2015-06-151-4/+8
| | | | Run that processor before inline processor to fix the test failure.
* 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
|
* 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
| |
* | added support for zero row tablespieterprovoost2015-04-051-2/+2
|/
* smarty: Add back special case for decade abbreviationsDmitry Shachnev2015-03-181-0/+4
| | | | | | | | | | 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.
* 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-081-1/+1
|
* Removed `yaml` option from meta-data extension.Waylan Limberg2015-03-081-34/+6
| | | | | 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-241-2/+2
| | | | 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-191-1/+1
|
* 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.
* Added a 'use_pygments' config option to CodeHilite.Waylan Limberg2015-02-051-7/+10
| | | | | | | | | 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-051-9/+11
| | | | | | | | | 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-313-18/+28
| | | | | | | | | 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.
* 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.
* HeaderId Extension marked as Pending Deprecation.Waylan Limberg2015-01-012-69/+74
| | | | | | | | | | | | | | | | | | | | 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.
View Lorry Controller Status