delta/python-markdown.git/tests/misc/em_strong_complex.html, branch inline github.com: waylan/Python-Markdown.git smart_emphasis keyword > legacy_em extension. 2015-04-22T23:53:49+00:00 Waylan Limberg waylan.limberg@icloud.com 2015-04-08T01:01:55+00:00 8dcfb14f705a92d134c3900cb344e3dd5df99d7b The smart_strong extension has been removed and its behavior is now the default (smart em and smart strong are the default). The legacy_em extension restores legacy behavior. This completes the removal of keywords. All parser behavior is now modified by extensions, not by keywords on the Markdown class. 
The smart_strong extension has been removed and its behavior is now the
default (smart em and smart strong are the default). The legacy_em
extension restores legacy behavior.

This completes the removal of keywords.  All parser behavior is now modified
by extensions, not by keywords on the Markdown class.
Better nested STRONG EM support. 2014-09-26T14:29:48+00:00 Waylan Limberg waylan.limberg@icloud.com 2014-09-25T20:07:07+00:00 8358bb3c569026d9775859bcdbd2611fc9499420 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. 
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.