summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Round out tests of valid markup.htmlWaylan Limberg2019-03-111-2/+232
| | | | There are some design desisions to make as noted in comments.
* More tests.Waylan Limberg2019-03-081-1/+227
|
* Add some new testsWaylan Limberg2019-03-071-0/+310
|
* Optimize several regexes from quadratic time to linear timeAnders Kaseorg2019-03-061-1/+1
| | | | | | Part of the discussion in #798. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* Add support for a range to toc_depth.Klaus Mueller2019-02-221-0/+55
| | | | Closes #786.
* Handle overlapping raw HTML matches (#770)Philip Trauner2019-02-071-0/+53
| | | | | Recursively run substitution to handle overlapping matches. Fixes #458.
* Emphasis pattern treats newlines as whitespace (#785)Waylan Limberg2019-02-071-0/+86
| | | | | | All whitespace characters should be treated the same by inline patterns. Previoulsy, emphasis patterns were only accounting for spaces, but not other whitepsace characters such as newlines. Fixes #783.
* Allow hashes to be escaped in headers (#763)Isaac Muse2018-12-221-0/+20
| | | | | Adjust pattern to allow for escaped hashes, but take care to not treat escaped escapes before hashes as escaped hashes. Close #762.
* Use a PEP562 implementation for deprecating attributes (#757)Isaac Muse2018-12-221-2/+2
| | | Use a vendored Pep562 backport to simulate Python 3.7's new PEP 562 feature. For Python3.7 and later, default to the official implementation.
* Fix typos in tests namesDmitry Shachnev2018-12-191-3/+3
|
* Collapse all whitespace in reference ids (#743)Isaac Muse2018-10-301-0/+37
| | | Previously only newlines preceded by whitespace were collapsed. Fixes #742.
* Deprecate version and version_info (#740)Isaac Muse2018-10-251-0/+39
| | | | This essentially implements the closest we can get to PEP 562 which allows for modules to control `__dir__` and `__getattr__` in order to deprecate attributes. Here we provide a wrapper class for the module in `util`. If a module has attributes that need to deprecated, we derive from the wrapper class and define the attributes as functions with the `property` decorator and the provided `deprecated` decorator. The class is instantiated with the module's `__name__` attribute and the class will properly replace the module with the wrapped module. When accessing the depracted attributes, a warning is raised. Closes #739.
* Ensure block elements are defined per instancefacelessuser2018-10-091-0/+12
| | | | Block level elements should be defined per instance, not as base class variables.
* foot note adjustments (#728)Isaac Muse2018-10-099-2455/+2496
| | | | | | Add a config to set the footnote separator. Also remove rel/rev as they aren't really compatible with HTML5 and we already have classes set for refs and backrefs. Fixes 723.
* Fix double escaping of block code (#727)Isaac Muse2018-10-071-0/+92
| | | | | Fixes #725
* Add a test for the markdown/serializers.py changeDmitry Shachnev2018-09-251-0/+4
|
* Make ENTITY_RE support hexadecimal entitiesissue712Dmitry Shachnev2018-09-251-0/+44
| | | | Fixes #712.
* Support custom labels in TOC. (#700)Waylan Limberg2018-09-051-9/+25
| | | | | | | | New `toc_tokens` attribute on Markdown class. Contains the raw tokens used to build the Table of Contents. Users can use this to build their own custom Table of Contents rather than needing to parse the HTML available on the `toc` attribute of the Markdown class.
* Move isBlockLevel to class. (#693)Waylan Limberg2018-07-311-3/+4
| | | | | Allows users and/or extensions to alter the list of block level elements. The old implementation remains with a DeprecationWarning. Fixes #575.
* Deprecate md_globals from extension API. (#697)Waylan Limberg2018-07-311-2/+2
| | | | | | In the past, most of the config was defined using globals. Today all of the config is held on the class instance. Therefore, the `md_globals` parameter is no longer necessary.
* Refactor options testsWaylan Limberg2018-07-314-10/+12
|
* smart_emphasis keyword > legacy_em extension.Waylan Limberg2018-07-317-7/+43
| | | | | | | | | The smart_strong extension has been removed and its behavior is now the default (smart em and smart strong are the default). The legacy_em extension restores legacy behavior (no smart em or smart strong). This completes the removal of keywords. All parser behavior is now modified by extensions, not by keywords on the Markdown class.
* Remove lazy_ol keyword. Use sane_lists extension instead.Waylan Limberg2018-07-315-38/+22
| | | | This was adapted from 11408e50 of the md3 branch.
* Removed unnessecary no attributes test. (#694)Waylan Limberg2018-07-313-7/+0
| | | This was missed in #683.
* Fix double escaping of amp in attributes (#670)Isaac Muse2018-07-295-2/+21
| | | | | | | | | | Serializer should only escape & in attributes if not part of &amp; Better regex avoid Unicode and `_` in amp detection. In general, we don't want to escape already escaped content, but with code content, we want literal representations of escaped content, so have code content explicitly escape its content before placing in AtomicStrings. Closes #669.
* Consistent copyright headers.Waylan Limberg2018-07-2716-3/+341
| | | | Fixes #435.
* Replace homegrown OrderedDict with purpose-built Registry. (#688)Waylan Limberg2018-07-271-147/+212
| | | | | | | | | | | | | | | | | | | All processors and patterns now get "registered" to a Registry. Each item is given a name (string) and a priority. The name is for later reference and the priority can be either an integer or float and is used to sort. Priority is sorted from highest to lowest. A Registry instance is a list-like iterable with the items auto-sorted by priority. If two items have the same priority, then they are listed in the order there were "registered". Registering a new item with the same name as an already registered item replaces the old item with the new item (however, the new item is sorted by its newly assigned priority). To remove an item, "deregister" it by name or index. A backwards compatible shim is included so that existing simple extensions should continue to work. DeprecationWarnings will be raised for any code which calls the old API. Fixes #418.
* Add toc_depth parameter to toc extensionJesús Fernández2018-07-241-0/+54
|
* Add the possibility to set additional classesWhiteWinterWolf2018-07-242-0/+17
| | | | | | | | | | | | | | | | | Additional CSS classes names can be appended to the admonition name using spaces as separators. The following markdown: !!! note floatright This is a floating note. Generates the following HTML code: <div class="admonition note floatright"> <p class="admonition-title">Note</p> <p>This is a floating note.</p> </div>
* Moved enable_attributes keyword to extension: legacy_attrs.Waylan Limberg2018-07-2412-37/+55
| | | | | | | If you have existing documents that use the legacy attributes format, then you should enable the legacy_attrs extension for those documents. Everyone is encouraged to use the attr_list extension going forward. Closes #643. Work adapted from 0005d7a of the md3 branch.
* Improve serializer test coverageWaylan Limberg2018-07-241-6/+64
| | | | | | | | | 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-0/+29
| | | | Fixes #679.
* Implement reset() for Meta extension (#672)Glandos2018-06-191-0/+14
| | | | Fixes #671
* Better check of allowed TOC location #639 (#641)Charles de Beauchesne2018-03-081-0/+35
|
* Only strip spaces in tables (#644)Isaac Muse2018-02-222-0/+43
| | | | | Strip only the space character and not things like nbsp in tables. Fixes #635.
* Simplify output_formats to html and xhtml.Waylan Limberg2018-01-251-3/+3
| | | | | | | | | | | 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-176-22/+242
| | | | 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.
* Improve test coverage.Waylan Limberg2018-01-131-2/+56
|
* Correct spelling mistakes.Edward Betts2018-01-1313-13/+13
|
* Refactor Extension loading (#627)Waylan Limberg2018-01-123-103/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 deprecated HeaderId Extension.Waylan Limberg2018-01-111-54/+0
| | | | Use the TOC extension instead.
* Removed deprecated safe_mode.Waylan Limberg2018-01-1120-532/+2
|
* Removed support for deprecated config in ext name.Waylan Limberg2018-01-111-7/+0
|
* Removed deprecated support for positional args.Waylan Limberg2018-01-111-5/+5
|
* Switch from nose to unittestWaylan Limberg2018-01-0812-556/+213
| | | | | | | | | | | | | | | 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-086-0/+1305
| | | | | | | | | | | | | | | | | | 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.
* Fix raw html reference issue (#585)Isaac Muse2018-01-042-0/+186
| | | | | | | | | | | | | | 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.
* Warnings should cause tests to fail.Waylan Limberg2018-01-041-0/+7
|
* Switch docs to MKDocs (#602)Waylan Limberg2017-12-062-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | 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-231-0/+52
| | | | | 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.