aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Clean up some docs formatting.Waylan Limberg2017-09-182-8/+9
|
* Switch to codecov from coverallsWaylan Limberg2017-09-083-3/+11
| | | | | | Note that we install coverage<4.0 in travis because test-requirements.txt is installing the same in the tox environments. The .coverage file format changed in 4.0.
* Manually define travis matrix.Waylan Limberg2017-09-071-7/+12
| | | | | | | | Travis-CI no longer has all supported Python versions installed by default. Each version needs to be set via the `python` setting. However, we don't want a matrix where every Python version runs with every `TOXENV`. Therefore, we now manually define the matrix so that the Python version is properly matched with the TOXENV.
* Adjust for new PyPI changesWaylan Limberg2017-08-172-3/+2
|
* Merge remote-tracking branch 'upstream/master'2.6.9Waylan Limberg2017-08-170-0/+0
|\
| * Upped version to 2.6.9Waylan Limberg2017-08-172-1/+5
| |
* | Upped version to 2.6.9Waylan Limberg2017-08-172-1/+5
|/
* GitHub/waylan => GitHub/Python-Markdown orgWaylan Limberg2017-08-1714-19/+18
|
* fix DeprecationWarning: invalid escape sequenced9pouces2017-07-251-1/+1
|
* fix DeprecationWarning: invalid escape sequenced9pouces2017-07-252-4/+4
|
* Fix typo s/Goggle/Google/Tim Chase2017-06-031-1/+1
|
* Fix a silly formatting error in README.Waylan Limberg2017-04-261-1/+1
|
* Added link to Code of Conduct in READMEWaylan Limberg2017-04-261-0/+8
|
* Add a code of conduct.Waylan Limberg2017-04-251-0/+50
| | | | | See http://contributor-covenant.org. I've adopted version 1.3 as I find 1.4 overly complex and lengthy.
* Update badgesWaylan Limberg2017-04-251-1/+1
|
* Exclude all nested test data from statsWaylan Limberg2017-04-251-7/+7
| | | See http://stackoverflow.com/questions/42544813/paths-not-excluded-from-github-language-statistics
* Exclude test data from project stats.Waylan Limberg2017-04-251-0/+7
| | | See https://github.com/github/linguist#my-repository-is-detected-as-the-wrong-language
* The location keyword of OrderedDict.add is not optional.Waylan Limberg2017-03-091-1/+1
| | | Fixes #554.
* Added footnote BACKLINK_TEXT test.Waylan Limberg2017-03-081-0/+24
|
* Loosen whitespace requirements for admonitions.Waylan Limberg2017-03-053-2/+18
| | | | | | | Also consume to the end of the first line of any admonition. Everything after the title is discarded. However, the only thing that will match should be whitespace so it should be a non-issue. Fixes #550.
* Fix regression of single column tables (#540)Isaac Muse2017-01-263-11/+169
| | | | | | Single column tables are valid tables, so add back in the accidentally removed functionality of allowing single column tables, but with one exception -- table bodies should not render empty (an empty `<tbody>` is invalid HTML. Fixes #539.
* Upped version to 2.6.8.2.6.8-finalWaylan Limberg2017-01-252-2/+3
|
* Fix HTML parse with empty lines (#537)Isaac Muse2017-01-243-1/+29
| | | | | | | If both open and close was not found in first block, additional blocks were evaluated without context of previous blocks. The algorithm needs to evaluate a buffer with the left bracket present. So feed in all items and get the right bracket, then adjust the data_index to be relative to the last block. Fixes #452.
* Fix footnote parsing of footnote content (#536)Isaac Muse2017-01-233-13/+78
| | | | | | | Fixes #412 and #493. First we parse footnote content as its own document avoid quirks with using li as a parent. Second, we surround placeholders with STX and ETX to prevent them from interfering with inline parsing; this is also consistent with how placeholders are used everywhere else in Python Markdown.
* Create additional references for duplicate footnotes (#534)Isaac Muse2017-01-233-5/+115
| | | | | | Track when we find duplicate footnote references and create unique ids for them. Then add an additional tree-processor after inline to go back and update the footnotes with additional back references that link to the duplicate footnote references. Fixes #468.
* Fix hr recursion issue (#535)Isaac Muse2017-01-233-2/+18
| | | | | | | HRProcessor tried to access a member variable after recursively calling itself. In certain situations HRProcessor will try to access its member variable containing its match, but it will not be the same match that call in the stack expected. This is easily fixed by storing the match locally *before* doing any recursive work.
* Better inline code escaping (#533)Isaac Muse2017-01-205-10/+42
| | | | | This aims to escape code in a more expected fashion. This handles when backticks are escaped and when the escapes before backticks are escaped.
* Tables: Improvements (#530)Isaac Muse2017-01-195-30/+172
| | | | | | | Tables now handle escaped pipes when testing, in table borders, and in the inline content. To achieve properly, a bug had to be fixed related to appending escaped chars to the Markdown class. Now appended chars only appear in the current instance. Lastly the first backtick in a table can be escaped rounding out the last corner case.
* Update fenced code extension to match codehilite lang regex. (#529)Waylan Limberg2017-01-181-1/+1
| | | Related to #527.
* codehilite: detect languages with funny names (#527)Grant Mathews2017-01-171-1/+1
| | | Extend the language regex to match things like 'C#' and 'VB.Net'.
* Recognize <main> as an HTML5 block level tag. (#525)daniel-j-mac2017-01-171-1/+1
|
* Better handling of backticks in tables (#524)Isaac Muse2017-01-113-41/+102
| | | | At some point the logic of counting backticks and determining if they are odd or even was used to parse a row's text into cells. Unfortunately this approach broke expected code parsing logic in a table. We essentially traded one bug for another. This fixes table backtick handling and restores sane backtick logic while preserving existing fixes. (issue #449)
* Fix aspell silently failing (#523)Isaac Muse2017-01-111-0/+1
| | | Travis should checkout aspell-en (issue #521)
* command line (#517)Ben Petty2016-12-231-1/+1
| | | add . before `codehilite` to generate a proper css output (to reference the codehilite class)
* Spelling error (#516)Ben Petty2016-12-231-1/+1
| | | should say `pygmentize` not `pygmetize` on line 50
* Add blank lines after toplevel function definitions.Dmitry Shachnev2016-11-184-0/+5
| | | | This fixes warnings with pycodestyle ≥ 2.1, see PyCQA/pycodestyle#400.
* Fox formatting of extension_configs example.Waylan Limberg2016-11-171-7/+3
| | | Fixes #511. Thanks to @omiday for the report.
* lists are not tables - fixes #478 (#507)Adam Wood2016-10-263-4/+15
|
* 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-232-1/+3
|
* No need to test the same thing twice.Waylan Limberg2016-09-232-5/+2
| | | | Related to #498.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2016-09-238-11/+21
|\
| * Fix table alignment when seperator contains spaces (#489)eph2016-08-152-4/+5
| | | | | | | | | | | | | | | | | | | | * Fix table alignment when seperator contains spaces eg. seperator like "------ | :----- | :----: | -----: | ------" * Update tests for table * Delete the newline at the end of tables.html
| * Merge pull request #485 from facelessuser/masterWaylan Limberg2016-07-263-3/+9
| |\ | | | | | | Fix image titles not following spec
| | * Fix image titles not following specfacelessuser2016-07-263-3/+9
| |/ | | | | | | | | 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.
| * Merge pull request #483 from mitya57/masterWaylan Limberg2016-06-133-3/+6
| |\ | | | | | | Fix another issue with attribute lists (with multiple ‘=’ signs)
| | * Fix another issue with attribute lists (with multiple ‘=’ signs)Dmitry Shachnev2016-06-133-3/+6
| |/
* | Don't allow equal signs in attr_list keys.Waylan Limberg2016-09-233-4/+7
| | | | | | | | | | | | 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.
* | Fix a few spelling errors.Waylan Limberg2016-09-231-3/+3
|/