Re: [Python-markdown-discuss] Overriding Functions, etc.

[Waylan L. <wa...@gm...>]

Ben Wilson wrote:
[snip]
> PmWiki has a situation where markups may be added willy-nilly while
> maintaining order. It would be rather radical to introduce to
> Markdown(). 

And not very pythonic. I remember the first time I realized how PmWiki 
did some very OO like things without OO code. For PHP it was amazing - 
and a pleasure to work with. Especially considering PHP's OO sytax. Uhg!

But if one tried to use PmWiki's approach in python, it would probably 
be more work than it's worth. A subclass of dict which maintains order 
or a class wrapping a list of tuples would be much less effort -- and 
more pythonic. For that matter, it wouldn't all that difficult to build 
a class from scratch for such a purpose.

[snip]
> want the conversion to occur before/after/during another item. I
> mention PmWiki only because I'm very familiar with its approach and
> know its author seeks ease-of-customization. Markdown() generally does
> not mean to be as customizable as it follows the Markdown standard
> format.

Ahh, now I know why your name seemed so familiar. Although I've been out
of the (PmWIki) loop for about a year now. It is true that Markdown does not
come close to PmWiki. If you're looking for more power, perhaps you 
should look at reStructuredText [1]. It seems to be the python default 
for markup, is easily extendable [2], and will output LaTex [3]. 
Personally, I prefer Markdown for its simplicity, but you seem to want 
power which brings more complexity. Imo, using an establish markup 
language (rest) is better than building your own custom creation.

[1]: http://docutils.sourceforge.net/rst.html
[2]: http://docutils.sourceforge.net/docs/howto/rst-directives.html
[3]: http://docutils.sourceforge.net/docs/user/latex.html

-- 
Waylan Limberg
wa...@gm...