summaryrefslogtreecommitdiff
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
...
* Improve serializer test coverageWaylan Limberg2018-07-241-14/+3
| | | | | | | | | Should be 100% coverage now. The ProcessingInstruction needed to be imported directly from ElementTree as PY27 was using a PIProxy which resulted in a bug. Interestingly, PY3 worked fine. Also removed the encoding code as it was not used. Besides it was only ever accessable from a private function.
* Simplify namespace support in serializer.Waylan Limberg2018-07-241-127/+48
| | | | Fixes #679.
* Implement reset() for Meta extension (#672)Glandos2018-06-191-0/+5
| | | | Fixes #671
* Fix typo.Amal Murali2018-05-071-1/+1
|
* Update block level elements.Waylan Limberg2018-03-161-10/+13
| | | | | Also refactor from regex to a list and add comments to explain why the elements are in the list for future reference. Fixes #543.
* Better check of allowed TOC location #639 (#641)Charles de Beauchesne2018-03-081-10/+12
|
* Only strip spaces in tables (#644)Isaac Muse2018-02-221-5/+5
| | | | | Strip only the space character and not things like nbsp in tables. Fixes #635.
* Simplify output_formats to html and xhtml.Waylan Limberg2018-01-252-20/+6
| | | | | | | | | | | We started with the numbers before HTML5 was a thing and we thought there might be an XHTML2. Today, we know that all we have are HTML style tags and XHTML style tags. Nothing else really matters in the real world. Note that if '(x)html1' '(x)html4' or '(x)html5' are passed in, the number is stripped/ignored. Users shouldn't need to change their code for this.
* Flexible inline (#629)Isaac Muse2018-01-179-161/+435
| | | | Add new InlineProcessor class that handles inline processing much better and allows for more flexibility. This adds new InlineProcessors that no longer utilize unnecessary pretext and posttext captures. New class can accept the buffer that is being worked on and manually process the text without regex and return new replacement bounds. This helps us to handle links in a better way and handle nested brackets and logic that is too much for regular expression. The refactor also allows image links to have links/paths with spaces like links. Ref #551, #613, #590, #161.
* Remove deprecated support for Extension args.Waylan Limberg2018-01-1317-73/+45
| | | | | | | | In the past Markdown used to pass extension config settings to the Extension class via a positional argument named `config`. That was deprecated in 2.6 in favor of using keyword arguments (`**kwargs`). Support has been completely dropped. Only keyword arguments are accepted.
* Improve test coverage.Waylan Limberg2018-01-1319-53/+22
|
* Correct spelling mistakes.Edward Betts2018-01-138-12/+12
|
* Refactor Extension loading (#627)Waylan Limberg2018-01-122-67/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Deprecated naming support is removed: * Removed special treatment for modules in `markdown.extensions` * Removed support for `mdx_` prefixes. Support for Entry Point names added: Support for "short names" are now implemented with entry points. Therefore all the users who call extension names as `toc` will not get errors as the builtin extensions all have entry points defined which match the old "short names" for modules in `markdown.extensions`. The benefit is that any extension can offer the same support without requiring the user to manually copy a file to that location on the file system (way to many extension authors have included such instructions in their installation documentation). The one odd thing about this is that we have been issuing a DeprecationWarning for short names and now they are fully supported again. But I think it's the right thing to do. Support for using dot notation is not removed. After all, it was never deprecated. And we shouldn't "force" entry points. There are plenty of reasons why users may not want that and not all of them can be resolved by using class instances instead. All of the following ways to load an extension are valid: # Class instance from markdown.extensions.toc import TocExtension markdown.markdown(src, extensions=[TocExtension()] # Entry point name markdown.markdown(src, extensions=['toc']) # Dot notation with class markdown.markdown(src, extensions=['markdown.extensions.toc:TocExtension']) # Dot notation without class markdown.markdown(src, extensions=['markdown.extensions.toc'])
* Removed some Py2.4-2.6 specific code.Waylan Limberg2018-01-112-21/+2
|
* Removed deprecated HeaderId Extension.Waylan Limberg2018-01-111-97/+0
| | | | Use the TOC extension instead.
* Removed deprecated safe_mode.Waylan Limberg2018-01-1111-128/+24
|
* Removed support for deprecated config in ext name.Waylan Limberg2018-01-111-19/+2
|
* Removed deprecated support for positional args.Waylan Limberg2018-01-111-32/+4
|
* Moved core to core.pyWaylan Limberg2018-01-113-486/+521
| | | | | | __version__ is now in __init__.py (as is should be) and the core is defined in core.py. Other than version, __init__.py is just a dummy which imports the pieces we make public.
* Switch from nose to unittestWaylan Limberg2018-01-081-1/+124
| | | | | | | | | | | | | | | All file-based tests are now defined as unittest test cases via a metaclass which walks a directory and builds a unittest for each pair of test files. To run the tests just run `python -m unittest discover tests`. Or use tox as the tox config has been updated to run the new tests and all nose specific code has been removed. The test generator tools have been removed as well. If any changes or additions need to be made to tests, they should be implemented using the new framework rather than with the file-based tests. Eventually, only the PHP and pl tests should remain as file-based tests.
* Provide new testing framework.Waylan Limberg2018-01-081-0/+44
| | | | | | | | | | | | | | | | | | As a part of the Markdown lib, test tools can be used by third party extensions. Also keeps test dir clean as it only contains actual tests. More work in this vein to come as the need for Nose is removed. Tests are defined as Unittests rather than in text files allowing features to be more easily broken into units and run individually. Based completely on standard lib unittest with no external dependencies. Use `python -m unittest tests.test_syntax` to run. Pulled some tests from https://github.com/karlcow/markdown-testsuite. Many more test units to pull from that source. As we encounter the need to edit an existing textfile-based test, or add a new test, a new test should be created with this framework and the old test should be deleted. Also need to delete existing testfile-based tests which are covered in the new tests included here.
* Version to 3.0.devWaylan Limberg2018-01-081-1/+1
| | | | | Development of version 3.0 starts here. Any bugfixes that should be applied to 2.x should be backported to the 2.6 branch.
* Up version to 2.6.11 (#620)2.6.11Waylan Limberg2018-01-041-1/+1
|
* Fix raw html reference issue (#585)Isaac Muse2018-01-043-1/+17
| | | | | | | | | | | | | | Preserve the line which a reference was on to prevent raw HTML indexing issue. Fixes #584. Prevent raw HTML parsing issue in abbr and footnotes Peserve abbreviation line when stripping and preserve a line for each footnote block. Footnotes should also accumulate the extraneous padding. Test extra lines at the end of references Strip the gathered extraneous whitespace When processing footnotes, we don't actually care to process the extra whitespace at the end of a footnote, but we want it to calculate lines to preserve.
* Avoid DeprecationWarnings for etreeWaylan Limberg2018-01-042-5/+5
| | | | Fixes #618.
* Make sure regex patterns are raw strings (#614)Isaac Muse2018-01-024-19/+19
| | | Python 3.6 is starting to reject invalid escapes. Regular expression patterns should be raw strings to avoid having regex escapes being mistaken for invalid string escapes. Fixes #611.
* [Footnote extension] Add a way to customize the backlink title (#616)Jorge Maldonado Ventura2017-12-221-2/+7
| | | Fixes #610.
* Upped version to 2.6.102.6.10Waylan Limberg2017-12-071-1/+1
| | | | | This version was released to force PyPI to point to the new docs location. Closes #601. The old PyPI hosted docs can be deleted after this.
* Switch docs to MKDocs (#602)Waylan Limberg2017-12-0619-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | Fixes #601. Merged in 6f87b32 from the md3 branch and did a lot of cleanup. Changes include: * Removed old docs build tool, templates, etc. * Added MkDocs config file, etc. * filename.txt => filename.md * pythonhost.org/Markdown => Python-Markdown.github.io * Markdown lint and other cleanup. * Automate pages deployment in makefile with `mkdocs gh-deploy` Assumes a git remote is set up named "pages". Do git remote add pages https://github.com/Python-Markdown/Python-Markdown.github.io.git ... before running `make deploy` the first time.
* Feature ancestry (#598)Isaac Muse2017-11-232-11/+48
| | | | | Ancestry exclusion for inline patterns. Adds the ability for an inline pattern to define a list of ancestor tag names that should be avoided. If a pattern would create a descendant of one of the listed tag names, the pattern will not match. Fixes #596.
* Fix new flake8 722 errorfacelessuser2017-10-261-1/+1
|
* Upped version to 2.6.9Waylan Limberg2017-08-171-1/+1
|
* 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
|
* Loosen whitespace requirements for admonitions.Waylan Limberg2017-03-051-2/+2
| | | | | | | 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-261-9/+40
| | | | | | 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-251-1/+1
|
* Fix HTML parse with empty lines (#537)Isaac Muse2017-01-241-1/+7
| | | | | | | 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-231-13/+20
| | | | | | | 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-231-5/+93
| | | | | | 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-231-2/+3
| | | | | | | 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-201-5/+9
| | | | | 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-192-29/+56
| | | | | | | 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-111-40/+62
| | | | 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)
* Add blank lines after toplevel function definitions.Dmitry Shachnev2016-11-183-0/+3
| | | | This fixes warnings with pycodestyle ≥ 2.1, see PyCQA/pycodestyle#400.
* lists are not tables - fixes #478 (#507)Adam Wood2016-10-261-1/+2
|
View Lorry Controller Status