| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes #184. Also delted some commented out code I missed in previous commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
| |
|
|\
| |
| | |
Prevent javascript:// URLs
|
|/ |
|
|\
| |
| | |
Enable attributes inside image references
|
|/ |
|
|\
| |
| | |
Support disabling documentation build in 'build' command
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Without this, all SyntaxTests would fail from a git checkout on Windows.
On other systems, it should have no effect.
|
|
|
|
| |
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)
|
|
|
|
| |
crash the serealizer.
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Fixed pyflakes warnings
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| | |
Thanks @mitya57.
|
| |\
| | |
| | | |
Improve docs/extensions/index.txt so that the name for each extension is properly identified.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
| |
| |
| | |
only of an Element - rather than the html which just gets html escaped in the output anyway.
|
| | |
|
| |
| |
| |
| | |
placeholder is an Elementtree Element.
|
| |\
| | |
| | | |
Fix the link in docs' bottom panel
|
| |/ |
|
| | |
|
|/ |
|
| |
|
| |
|