delta/python-markdown.git/markdown/inlinepatterns.py, branch strongem

Better nested STRONG EM support.

2014-09-25T20:07:07+00:00

Addresses most of #253. Thanks to @facelessuser for the tests. Although
the tests currently failing may or may not be valid. It could be that
the failing tests will be removed with the expectation that when a
document author does that, they can see that it doesn't work and
change their document to something that works. But I need to go
through them before I'm sure.

Fix the lost tail issue in inlineprocessors.

2014-09-25T18:00:51+00:00

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.

Removed some old code

2014-08-25T20:19:37+00:00

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.

Mark a few more lines with 'no cover' - missed them the first time through. The rest should have test cases added.

2014-07-12T01:46:51+00:00

Marked a bunch of lines as 'no cover'. Coverage at 91%

2014-07-12T01:24:30+00:00

No longer percent encode spaces in urls.

2014-01-10T04:43:52+00:00

The current implementation was wrong as it also percent encoded query strings
(which should be plus encoded) and calling urllib.quote on the path (and
urllib.quote_plus on the query string) assumes the url is not already encoded.
What if the document author pasted a url that was already encoded? She probably
did not intend for `%20` to become `%2520`. Or did she? It is now clear to me
why many implementation do nothing to urls. Just pass them though as-is. To bad
if they are not valid HTML. HTML authors have to encodee their own urls, so I
guess markdown authors have to as well.

Only escape ESCAPED_CHARS.

2014-01-10T03:41:30+00:00

Leave all other chars prefaced by a backslash alone. Fixes #242.
Not sure why I thought that I needed to add another backslash.
Thanks for the report and the test case @mhubig.

Fixed parsing of brackets within inline image titles.

2014-01-05T14:20:44+00:00

Future imports go after the docstrings

2013-03-18T20:54:14+00:00

A `from __future__ import ...` statement must go after any docstrings;
since putting them before the docstring means the docstring loses its
magic and just becomes a string literal.  That then causes a syntax
error if there are further future statements after the false docstring.

This fixes issue #203, using the patch provided by @Arfrever.

Now using universal code for Python 2 & 3.

2013-02-27T14:10:47+00:00

The most notable changes are the use of unicode_literals
and absolute_imports. Actually, absolute_imports was the
biggest deal as it gives us relative imports. For the first
time extensions import markdown relative to themselves.
This allows other packages to embed the markdown lib in a
subdir of their project and still be able to use our
extensions.