I just wanted to let you know that I have included markdown2 into the
latest release of web2py under gluon/contrib/. web2py is distributed
in source and binary forms under GPL2 with a commercial exception.

I understand the license of markdown2 allows me to include it but I
wanted to make sure that you are fine with it.

You are acknowledged in the thanks page:

 http://mdp.cti.depaul.edu/examples/default/thanks

You can also find an example of usage of markdown2 within web2py here

 http://mdp.cti.depaul.edu/examples/default/examples (#14)

Massimo

I am not so sure that underscores for emphasis should be dropped altogether.
I don’t use them myself, but I’ve seen people using underscores for this purpose
in ordinary email. And:

> …the single biggest source of inspiration for Markdown’s syntax
> is the format of plain text email.

Yes, perhaps ignoring middle-word emphasis (for underscores at least) should be done. However, I’d like to see John Gruber’s comments on that. I think it is important (for Markdown in general) that different Markdown implementations implement the same spec, so I want markdown2.py to produce the same output as Markdown.pl by default.

Personally I think that the use of underscores for emphasis (both internal to words and not) should be dropped from the Markdown “spec”, because they are an unnecessary duplication of using asterisk for the same thing. Definitely I support dropping internal-word emphasis (for the same reasons as in your discussion link).

Note that for Python code (which I, of course, commonly work with), variables like __init__, __repr__, __str__, etc. are very common, so just dropping internal-word emphasis still results in the same issue as bug_by_oversight.

I know python-markdown2 includes code-extra. I think the better solution is to mimic python-mardown1: it just ignores middle-word emphasis (there’s also some discussion)