Re: [Python-markdown-discuss] python-markdown, and wikis.

[Yuri T. <qar...@gm...>]

On Mon, Feb 4, 2008 at 8:37 PM, Waylan Limberg <wa...@gm...> wrote:

>  I'd say you nailed it. That about sums up the difference. With
>  python-markdown2, you'd need to hack the core to add or change
>  behavior. Personally, I'd much rather use python-markdown's extension
>  api. In fact if you run into a few dead ends, let us know. We may be
>  able to improve the api to make more things possible.

Hey, let a hundred flowers bloom...  I haven't been following
python-markdown2 development closely enough to say how much of an
effort it would be to hack it.  But Waylan is right that
python-markdown was designed with the assumption that people would
want something-but-not-quite like the standard behavior and that
extensibility and readability is more important than 100% compliance
with the Perl implementation or performance.  I've tried to keep both
in the acceptable range (and Waylan really helped with this recently),
but it hasn't been top priority.

Maybe at some point someone would find time to combine the best of
both worlds...

>  > but I was wondering
>  > if you had any suggestions of wikis that were using your project?

http://infogami.org/

We've even almost moved the python-markdown wiki to infogami, but then
this got stalled because I didn't have time to work out some minor
issues.

BTW, I am wondering if we should just add some a pattern for
wikilinks, perhaps [[...]] into markdown.py so that one would be able
to activate it with just a flag or something.

>  > definition term
>  > :  definition description
>  >
>  > If you don't handle them, how hard do you think it would be to create a
>  > plugin that would handle them?

Easy.  You should do it!

- yuri

-- 
http://sputnik.freewisdom.org/