aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Updated toc extension to work with changes @ 4ff74e3.Waylan Limberg2013-02-191-2/+2
|
* Ensure toc attribute is available on Markdown class.Waylan Limberg2013-02-193-5/+61
| | | | | | This appears to have recently been broken with the fixes in #191. This time I've added tests to prevent future breakage and added documentation to explain the behavior.
* Merge pull request #192 from benjaoming/masterWaylan Limberg2013-02-184-28/+45
|\ | | | | Little changes
| * adding test for out of order headlinesbenjaoming2013-02-183-0/+16
| |
| * Do not use assigned names "next" and "id", rename to order_toc_list and ↵benjaoming2013-02-181-18/+20
| | | | | | | | clean up code
| * Merge branch 'toc-fix'benjaoming2013-02-181-13/+12
|/|
| * code cleanupbenjaoming2013-02-181-13/+12
| |
* | Merge pull request #191 from benjaoming/toc-fixWaylan Limberg2013-02-171-63/+126
|\| | | | | Make TocTreeprocessor extendable and be gentle on badly structured headings
| * Make TocTreeprocessor extendable and be more gentle on badly structured headingsbenjaoming2013-02-171-63/+126
|/
* Allow better linenum override in CodeHiliteWaylan Limberg2013-02-144-20/+125
| | | | | | | | | | | Fixes #148. The "force_linenos" config setting of the CodeHilite extension has been marked as Pending Deprecation and a new setting "linenums" has been added to replace it. See documentation for the [CodeHilite Extension] for an explaination of the new "linenums" setting. The new setting will honor the old "force_linenos" if it is set, but it will raise a PendingDeprecationWarning and will likely be removed in a future version of Python-Markdown. [CodeHilite Extension]: extensions/codehilite.html
* Preserve all blank lines in code blocks.Waylan Limberg2013-02-142-14/+14
| | | | | | | | | | | | Fixes #183. Finally got this working properly. The key was using a regex substitution with non-overlapping matches that removed all whitespace from the begining of *all* blank lines when normalizing whitespace. Once I got that, I could simplfy the EmptyBlockProcessor and easily output one or two blank lines appropriately. A blank block gets two new lines (`'\n\n'`), while a block which starts with a newline gets one.
* Remove RSS Extension.Waylan Limberg2013-02-126-161/+8
| | | | | | Closes #143. If you would like to continue using the extension (not recomended), it is archived on [Github](https://gist.github.com/waylan/4773365).
* Build_docs script now uses new Admonition extension.Waylan Limberg2013-02-121-1/+1
|
* Allow capitalized Admonition title.Waylan Limberg2013-02-122-2/+2
| | | | | If an adminition title is capitalized, the html class on the div should still be lowercased.
* Update docs/release-2.3.txtWaylan Limberg2013-02-101-0/+8
|
* Noted in docs that admonitions are experimental.Waylan Limberg2013-02-101-1/+5
|
* Merge pull request #140 from slig/admonitionWaylan Limberg2013-02-109-48/+318
|\ | | | | Admonitions: Initial version. This is still considered beta and subject to change. Thanks for all the work @slig.
| * Better synthax description in the docs.Tiago Serafim2013-02-091-1/+1
| |
| * Merge branch 'master' into admonitionTiago Serafim2013-02-0953-256/+719
| |\ | |/ |/| | | | | | | Conflicts: docs/extensions/index.txt tests/extensions/test.cfg
* | Footnote ids contain dashes when outputing HTML5.Waylan Limberg2013-02-083-6/+14
| | | | | | | | | | Previously they contained colons - and they still do for HTML4 and XHTML. Fixes #180.
* | Updated docs to reflect extension loading best practices.Waylan Limberg2013-02-082-19/+50
| | | | | | | | Fixes #184. Also delted some commented out code I missed in previous commit.
* | Moved whitespace normalization to a preprocessor.Waylan Limberg2013-02-083-5/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #150 - at least as much as I'm willing to. This allows whitespace normalization to be overridable by the extension API. Yes, I realize that most other processors will also proabably need to be overniriden to work with any differant whitespace normalization - but I'm okay with that. As pointed out in #150, some processors have the tab length hardcoded in regexes. I'm willing to accept a working patch that fixes that - and keeps the regexes easy to override in a subclass (the provded patch moved them inside the __init__ method - which is not so easy to override in a subclass)). However, that is about the only additional change I'm willing to consider for this issue.
* | Added skeleton draft of Release Notes for 2.3Waylan Limberg2013-02-083-4/+37
| |
* | Cleaned up fixes for #183Waylan Limberg2013-02-083-1/+7
| | | | | | | | | | | | | | | | | | My previous commit (d5a94c2) broke a few things badly. Unfortunately I failed to run the complete test suite and didn't catch it. A bad regex was crashing the test suite. Also cleaned up a few other odds and ends from previous work on #183. Still loosing a few random empty lines in code blocks though. I suspect this may also fix #188.
* | HtmlBlockProcessor preserves empty linesWaylan Limberg2013-02-073-9/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | Partial fix for #183. This has the same effect on empty lines in code blocks as not using the html processor at all (which was eating some of the missing newlines as reported in issue #183). By doing `rsplit('\n\n')` the third newline (in each set of three) always ends up at the end of a block, rather than the begining - which it less of an issue for the html processor. Also updated tests to indicate final intended output, although they do not fully pass yet.
* | Preserve whitespace in empty linesWaylan Limberg2013-02-073-1/+68
| | | | | | | | | | | | | | | | Partial fix for #183. By preserving tabs at the start of empty lines in code blocks, the parser will retain those empty lines. Still does not work consistantly if the tab is missing!? Not sure why. Also added tests.
* | Preserve empty lines in code blocksWaylan Limberg2013-02-062-7/+8
| | | | | | | | | | | | Partial fix for #183. Some lines are still being lost. When the processors are run, one line is lost. When their calling code is comments out (completely skiped) a line is still lost if more than 3 exist in a row. Also need to add some tests for this.
* | nl2br and attr_list compatability.Waylan Limberg2013-02-065-3/+9
| | | | | | | | | | | | Fixes #177. When using both extensions, breaks (`<br>`) must have a linebreak (`\n`) after them before attr_list is run. This patch reorders the treeprocessors so that happens ('attr_list' runs after 'prettify' not before). Also had to alter headerid extension so it runs after 'prettify' or it would run before 'attr_list' if loaded before 'attr_list' by user.
* | Account for a paragraph that starts with a colon when processing def_listsWaylan Limberg2013-02-063-4/+50
| | | | | | | | Fixes #171. While that report provided an example of an unordered list item that started with a colon, any block that starts with a colon and has no siblings before it (paragraph as begining if document, list item, etc) all exhibit this same behavior. Following PHP Markdown Extra's lead, these are not definition items as they have no term before them.
* | Whitelisted known safe url schemes in safe_mode. A better fix for #185.Waylan Limberg2013-02-061-6/+7
| |
* | Merge pull request #185 from phihag/safemode-no-javascript-urlsWaylan Limberg2013-02-053-0/+8
|\ \ | | | | | | Prevent javascript:// URLs
| * | Forbid javascript:// URLs in safe modePhilipp Hagemeister2013-02-053-0/+8
|/ /
* | Merge pull request #182 from abackstrom/img-ref-attributesWaylan Limberg2013-01-283-0/+9
|\ \ | | | | | | Enable attributes inside image references
| * | Enable attributes inside image referencesAdam Backstrom2013-01-273-0/+9
|/ /
* | Merge pull request #178 from mgorny/masterWaylan Limberg2013-01-131-1/+12
|\ \ | | | | | | Support disabling documentation build in 'build' command
| * | Support disabling documentation build via --no-build-docs.Michał Górny2013-01-131-1/+12
|/ /
* | No longer support python 2.5Waylan Limberg2013-01-101-7/+1
| |
* | Github no longer offers Downloads - no need to upload any.Waylan Limberg2013-01-101-62/+0
| |
* | Improved the goals in docs.Waylan Limberg2013-01-101-3/+5
| |
* | Added a "goals" section to the docs.Waylan Limberg2013-01-101-2/+15
| | | | | | | | | | Now, when we receive feature requests that don't fit within the scope of the Python-Markdown project, we have something to point  to in response.
* | Added a list of known differences to the docs.Waylan Limberg2013-01-101-8/+44
| | | | | | | | | | | | | | | | | | | | | | Rather than constantly responding to new bug reports for known differences between Python-Markdown and other implementations, I've added this section to the docs to definitively state our position and point people to workarounds. I'm sure some people will still file reports, but at least I have something to point them to. If there are any I missed, I can always add them latter when they come up.
* | Better fix for #164. Works in Python 2 & 3.Waylan Limberg2012-12-181-4/+4
| |
* | Fixed #169. The new version stuff now works in python 2 & 3.Waylan Limberg2012-12-181-3/+12
| |
* | Testing framework now runs on Python 2 & 3 unmodified.Waylan Limberg2012-12-146-36/+46
| |
* | Normalize line endings in tests as git may alter them on Windows.Waylan Limberg2012-12-141-2/+3
| | | | | | | | | | Without this, all SyntaxTests would fail from a git checkout on Windows. On other systems, it should have no effect.
* | Fixed #165. Switched the order of treeprocessors when attr_list and headerid ↵Waylan Limberg2012-12-133-10/+20
| | | | | | | | extensions are used togeather. While this means headerid may alter IDs defined in attr_lists for uniqueness, automaticaly generated ids will not contain unparsed attr_lists. This is the lesser of two evils - and actually generates a more valid output (all IDs will be unique)
* | Fixed #164. attr_list extension attribute names are now sanitized and won't ↵Waylan Limberg2012-12-133-3/+16
| | | | | | | | crash the serealizer.
* | Upped version to 2.3.dev.Waylan Limberg2012-12-054-6/+46
| | | | | | | | | | Also refactored the version info to force PEP 386 compliance and to avoid the need to change the version in both the source and setup.py
* | Fixed #160. No `markdown=1` support in safe_mode.Waylan Limberg2012-12-051-2/+3
| | | | | | | | | | | | | | When in safe_mode, there is no raw html to contain `markdown=1` for processing, so there is no need to turn on that feature. The symptom reported in issue #160 appears to be a side effect of commit a2377e1129331430998de821ed3abf38247edca1.
* | Merge pull request #159 from mitya57/masterWaylan Limberg2012-11-0910-12/+4
|\ \ | | | | | | Fixed pyflakes warnings
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 15:42:56 +0000