aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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
| * Fix all pyflakes unused-import/unused-variable warningsDmitry Shachnev2012-11-099-11/+3
| |
| * docs/change_log.txt: add a missing `[`Dmitry Shachnev2012-11-051-1/+1
| |
* | Updated fix for #158 for Python <2.7Waylan Limberg2012-11-081-1/+1
| | | | | | | | | | | | | | Apparently, the `errors` keyword to encode was added in Python 2.7. In previous versions, it was just a positional argument. This should now work in all support versions. Thanks to @Gamma3000 for assistance in working through this issue.
* | Fixed #158. Now properly encoding output to stdout.Waylan Limberg2012-11-071-8/+7
|/ | | | | | | | This is another try at this problem. The trick is geting code that works with both Python 2 and Python 3. I think this does it. The only improvment I can see now is to catch any errors and customize the error message to sugg that the user set the environment variable PYTHONIOENCODING to the desired encoding before calling the commandline script.
* Merge branch 'master' of https://github.com/waylan/Python-Markdown2.2.1.finalWaylan Limberg2012-11-046-32/+90
|\
| * Fixed minor typo in attr_list docs. Waylan Limberg2012-11-041-1/+1
| | | | | | Thanks @mitya57.
| * Merge pull request #157 from mitya57/masterWaylan Limberg2012-11-033-27/+68
| |\ | | | | | | Improve docs/extensions/index.txt so that the name for each extension is properly identified.
| | * docs/basic.css: Improve CSS a bitDmitry Shachnev2012-11-031-8/+15
| | |
| | * docs/extensions/index.txt: make it clear what name to pass for extensionsDmitry Shachnev2012-11-031-19/+53
| | |
| | * Remove exec bit from extensions/fenced_code.pyDmitry Shachnev2012-11-031-0/+0
| |/
| * Fix silly typo in previous commit.Waylan Limberg2012-11-011-1/+1
| |
| * A better fix for #155. Unescaping inline placholders now returns the text ↵Waylan Limberg2012-11-011-6/+19
| | | | | | | | only of an Element - rather than the html which just gets html escaped in the output anyway.
| * Fixed #154. Inline placeholders in img alt text are now unescaped.Waylan Limberg2012-11-011-1/+1
| |
| * Fixed #155. Early unescaping of inline placeholders now works when the ↵Waylan Limberg2012-11-011-1/+5
| | | | | | | | placeholder is an Elementtree Element.
| * Merge pull request #156 from mitya57/masterWaylan Limberg2012-10-261-1/+1
| |\ | | | | | | Fix the link in docs' bottom panel
| | * Apply a fix from commit 3e6e70eb48 to the bottom panel as wellDmitry Shachnev2012-10-261-1/+1
| |/
* | Upped version to 2.2.1.Waylan Limberg2012-11-046-9/+24
| |
* | Fixed CodeHilite test when pygments is not installed.Waylan Limberg2012-11-041-1/+1
|/
* Fixed #153. Two spaces at end of paragraph is not a linebreak.Waylan Limberg2012-10-214-14/+6
|
* Fixed #152. Spaces in links are now escaped.Waylan Limberg2012-10-213-3/+4
|
* Fixed #151. Raw html matching is now case-insensitive.Waylan Limberg2012-10-213-2/+13
|
* Merge pull request #142 from mitya57/masterWaylan Limberg2012-09-091-0/+21
|\ | | | | Add `long_description` attribute to `data` in `setup.py`
| * Remove unneeded linkDmitry Shachnev2012-09-091-1/+0
| |
| * setup.py: Add `long_description` attribute to `data`Dmitry Shachnev2012-09-091-0/+22
|/ | | | so that there's no text breakage on PyPI page
* Fixed #141. Minor typo on wikilinks docs.Waylan Limberg2012-09-071-1/+1
| | | Thanks for the report.
* Merge pull request #139 from Grahack/patch-2Waylan Limberg2012-08-291-2/+2
|\ | | | | Typo: Boolen -> Boolean.
| * Typo: Boolen -> Boolean.Grahack2012-08-291-2/+2
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 14:59:30 +0000