Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

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

>> 1.  The wikilink behavior has changed in a non-backwards-compatible way.
>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they are not.
>>  Personally, I preferred the old way.

The new way is closer to what Wikipedia does, which is a big plus, I
think. However, perhaps it would make sense to make this configurable.
Right now we have

    label.replace(' ', '_')

in markdown/extensions/wikilinks.py

Both arguments to replace could perhaps be configurable, and the first
one should probably be treated as a regular expression. Alternatively,
we could have a config parameter that could be set to a function that
would be used to do the conversion, so you would have something like:

makeExtension(configs = {'make_url': lambda x: label.replace(' ', '')})

> Well, the reason is that this (PHP) is an already existing and highly
> distributed implementation. The idea is that one should be able to
> pass the same source documents through any implementation and get back
> the same result. So, I went with an already existing implementation.

I agree with this completely. I think it would be great to have a set
of extensions that get us as close as possible to PHP Markdown Extra.
People are free, however, to implement their own table extensions,
that have different behavior, and we can even add some of them to our
collections of extensions.

> Anyone is encouraged to branch and create their own extensions.

For extensions - definitely. Of course, it's good to always look for
opportunities for code reuse. E.g., instead of actually branching
code, it may be better to have a different extension that uses the
same module but just configures it differently.

- yuri

-- 
http://spu.tnik.org/