aboutsummaryrefslogtreecommitdiffstats
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
* Changed logging level when loading extensionsChris Topaloudis2014-10-241-1/+1
| | | So it suppresses messages for loaded extensions when its used as third party.
* Fix tail out of order issuefacelessuser2014-10-181-1/+1
| | | | | | | | | | | | This issue was discovered when dealing with nested inlines. In treeprocessors.py it was incorrectly handling tails. In short, tail elements were being inserted earlier than they were supposed to be. In order to fix this, the insertion index should be incremented by 1 so that when the tails are inserted into the parent, they will be just after the child they came from. Also added a test in nested-patterns to catch this issue.
* Use Pygments APIfacelessuser2014-10-041-10/+10
|
* Upped version to 2.5.12.5.1-finalWaylan Limberg2014-09-261-1/+1
| | | | Also removed an inacurate statement in the 2.5 release notes.
* Run Meta after whitespace normalizationWaylan Limberg2014-09-261-1/+1
| | | | Fixes #343. Thanks for the report @AlexJF.
* Better nested STRONG EM support.Waylan Limberg2014-09-261-2/+6
| | | | | | | | | Fixes #253. Thanks to @facelessuser for the tests. Although I removed a bunch of weird ones (even some that passed) from his PR (#342). For the most part, there is no definitive way for those to be parsed. So there is no point of testing for them. In most of those situations, authors should be mixing underscores and astericks so it is clear what is intended.
* Fix the lost tail issue in inlineprocessors.facelessuser2014-09-262-23/+26
| | | | | | See #253. Prior to this patch, if any inline processors returned an element with a tail, the tail would end up empty. This resolves that issue and will allow for #253 to be fixed. Thanks to @facelessuser for the work on this.
* Added a temp workwround for deprecated short ext names.Waylan Limberg2014-09-251-0/+4
| | | | | | | | | | | | As we chnaged the order in import trys for short names extensions (no dot syntax), an extra test was added to the import code for the occassion when a naming conflict exists. For example, if PyTables is installed (module name is tables) and the user tries to use the short name 'tables' instead of 'markdown.extensions.tables'. Fixes #341. Of course, this code will get ripped out when the old behavior is fully deprecated.
* Fixed TOC Option parsing.Waylan Limberg2014-09-251-2/+2
| | | | | | The new option parser assumes bool values if the default is bool or None. As the "title" option is not a bool value, it should default to an empty string rather than None. Fixes #347.
* Version 2.5-Final2.5-finalWaylan Limberg2014-09-121-1/+1
|
* Deprecate positional args for markdownFromFile also.Waylan Limberg2014-09-121-0/+4
|
* Code Blocks must always be AtomicStringsWaylan Limberg2014-09-081-1/+1
| | | | | | | | | | | | | | | | | | Fixes #340. The "inline" TreeProcessor runs before the "prettify" TreeProcessor, but the "smarty" TreeProcessor (wich is just another instance of `InlineProcessor`) runs after the "prettify" TreeProcessor. The problem was that the "prettify" TreeProcessor was losing the AtomicString quality of the text of code blocks (any operation on a string creates a new string. When that string is an AtomicString, the new string must explicitly be declared as an AtomicString. As the "prettify" TreeProcessor cleans up newlines on code blocks, it was changing the AtomicString to a normal string. And as `InlineProcessor` identifies what elements to skip solely by whether the text is an AtomicString, the "smarty" instance was running on code blocks. Importantly, I added a test of code blocks and spans for smarty, so this shouldn't break again.
* Mark "Safe Mode" as pending deprecation.Waylan Limberg2014-09-012-7/+22
| | | | | Both `safe_mode` and `html_replacement_test` keywords are pending deprecation, as are positional args. Closes #337.
* Mark special treatment of extension names as PendingDeprecationWaylan Limberg2014-08-292-7/+41
| | | | | | | | | | | | | | | | | The builtin extensions will no longer get special treatment and have the path ("markdown.extensions.") appended . The same applies for "mdx_" extensions. All names extension must provide the full path. Fixes #336. Also deprecating support for passing in extension config settings as part of the string name. The extension_configs keyword should be used instead. Fixes #335. Also raising PendingDeprecationWarnings for positional args or the "config" keyword on the Extension Class. Pass each setting as a seperate keyword instead. Docs and tests are updated. Still need to update extension API docs.
* More updates to test configs.Waylan Limberg2014-08-293-13/+18
| | | | | | | | | | | | | | The last few extensions were updated to accept dicts/**kwargs as configs and more tests were updated. Also updated extra to actually accept configs. Note that extra requires an extra level of dicts. First you need to indicate tha the settings are for extra, then, which extension extra wraps. I'm not crazy abount this, bit not sur ehow else to do it without making all the configs a global attribute on the Markdown class to that any extention can access any other extensions config settings. I don't think we wnat to do that. Also updated extra to use dot notation for the sub-extensions.
* Merge branch 'master' of https://github.com/waylan/Python-MarkdownWaylan Limberg2014-08-271-1/+1
|\
| * Fixed a small bug in --extension_configs CLI option.Waylan Limberg2014-08-251-1/+1
| | | | | | | | | | | | | | | | | | This needs to work with the JSON lib if PyYaml isn't available. Therefore, we can't catch a yaml specific exception. The tests are fine using a yaml specific exception as the yaml lib is required by the testing framework anyway. So yaml is always available when running the tests.
* | Allow named extensions to specify the Class NameWaylan Limberg2014-08-271-10/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you were to import the class like this: from path.to.module import SomeExtensionClass Then the named extension would be the string: "path.to.module:SomeExtensionClass" This should simplify loading extensions from the command line or template filters -- expecially when multiple extensions are defined in a single python module. The docs still need updating. I'm waiting to update the docs after implementing #335 and #336 as that will require a major refactor of that section of the docs anyway.
* | Refactored extension importing.Waylan Limberg2014-08-271-15/+23
|/ | | | | | | | | | | | | We now use importlib which means we no longer support Python 2.6. Also, this refactor properly imports third party extensions which reside at the root of PYTHONPATH. Previously, either `markdown.extensions.` or `mdx_` would be appended to any extension name that did not contain a dot, which required third party extensions to either be in submodules or use the old `mdx_` naming convention. This commit is also in preperation for #336. It will now be much easier to deprecate (and later remove) support for the old ways of handling extension names.
* Removed some old codeWaylan Limberg2014-08-251-4/+1
| | | | | | These couple lines were from an old - no longer used - method of stashing inlines. There is no need for it today. The if statement would never evaluate True.
* Fixed a bug in markdown.util.parseBoolValueWaylan Limberg2014-08-251-3/+3
| | | | | A couple scenarios with "None" were previously not accounted for. Also updated tests which guives us 100% for markdown/util.py
* Include __main__.py in coverage.Waylan Limberg2014-08-221-3/+3
|
* Added `--extension_configs` option to the CLI.Waylan Limberg2014-08-221-13/+37
| | | | | | | | | | The `--extension_configs` option must point to a YAML or JSON file. The contents of the file must parse to a Python Dict which will be passed to the `extension_configs` keyword of the `markdown.Markdown` class. Also added tests for all of the CLI option parsing options and updated documentation.
* Cleaned up some whitespace inconsistancies.Waylan Limberg2014-08-221-1/+1
|
* Standardized all extension header comments to a uniform format.Waylan Limberg2014-08-2117-446/+193
|
* 'http://packages.python.org/Markdown/' => ↵Waylan Limberg2014-08-2110-13/+13
| | | | 'https://pythonhosted.org/Markdown/'. The former redirects to the latter anyway. Might as well point to the actual destination.
* Upped version to 2.5-dev and started release notes.Waylan Limberg2014-08-201-1/+1
|
* Renamed 'smart_substitutions' option to 'substitutions'. Fixed a typo.Martin Altmayer2014-08-151-3/+2
|
* Fixed an old typo in the smarty extension and added a test case.Martin Altmayer2014-08-111-2/+2
|
* Replaced smart_lsquo etc. by a single option smart_substitutions which ↵Martin Altmayer2014-08-111-14/+32
| | | | allows to overwrite all substitution strings. Fixed line length in docs.
* Added options to the Smarty extension that configure the text that is used ↵Martin Altmayer2014-08-091-3/+10
| | | | to replace quotes. This makes it possible to use the correct quotes in languages other than English.
* Update extensions for Extension.__init__ refactorWaylan Limberg2014-07-3119-102/+100
| | | | | | | | | | | | | | | | | 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-7/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Mark a few more lines with 'no cover' - missed them the first time through. ↵Waylan Limberg2014-07-113-6/+6
| | | | The rest should have test cases added.
* Marked a bunch of lines as 'no cover'. Coverage at 91%Waylan Limberg2014-07-1112-31/+32
|
* smarty: add support for angled quotesDmitry Shachnev2014-06-191-0/+11
| | | | See <http://en.wikipedia.org/wiki/Guillemet>.
* Merge pull request #317 from mitya57/doctestsWaylan Limberg2014-06-167-37/+37
|\ | | | | Python 3.4 and fixes for doctests
| * Make doctests support Python 3Dmitry Shachnev2014-06-117-33/+33
| |
| * Fix a doctest in fenced_code.py.Andrey Rahmatullin2014-05-311-4/+4
| |
* | Fix #315: Change order of smarty patterns to make the test pass againDmitry Shachnev2014-06-081-2/+2
|/
* Merge pull request #311 from mitya57/masterWaylan Limberg2014-05-262-7/+14
|\ | | | | Make smarty extension work together with attr_list
| * Make smarty extension use its own InlineProcessorDmitry Shachnev2014-05-261-5/+11
| |
| * Make it easier to override list of inline patterns for InlineProcessorDmitry Shachnev2014-05-261-2/+3
| |
* | Support extensions as modules.Waylan Limberg2014-05-231-1/+1
| | | | | | | | | | | | | | | | | | | | Fixes #300. When a python module (.../__init__.py) is imported by `__import__` and the `from_list` argument is a unicode string (as is returned by rpartition), then an error is raised in Python 2.7. Force conversion to default string type (byte in 2.7 and unicode in 3) to avoid the error. For a full explaination, see issue [300](https://github.com/waylan/Python-Markdown/issues/300).
* | Upped version to 2.4.12.4.1-finalWaylan Limberg2014-05-221-1/+1
| |
* | Fix issue308 and fix (unrelated) failure to break out of nest loop.ryneeverett2014-05-212-22/+16
|/
* smarty: Fix test failure with Python 3.1 and 3.2. Fixes #295Dmitry Shachnev2014-03-111-1/+1
|
* smarty: Pass tuples, not iterable strings to the pattern.Dmitry Shachnev2014-03-111-3/+3
|
* added nav-tag as block level elementDavid2014-03-021-1/+1
|
* Upped version to 2.4 final.2.4-finalWaylan Limberg2014-02-161-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-05 22:10:25 +0000