Re: [Python-markdown-discuss] Announcing Definition List Extension - call for testing

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

>> The main markdown parser marked some methods with __'s... which is
>> supposed to be the indicator that the method is private.  So it's a
>> little bit disturbing that DefListParser is drilling into those
>> internals.  Perhaps it's indicative that those methods should be
>> exposed more, or that we need an extra hook point into the code?
>
> That's a valid point and one I've thought about as well.
> Unfortunately, I don't have a good answer yet. Part of my motivation
> in doing this extension was to raise these questions and see how
> things go.

What worries me more, actually, is the fact that the extension ends up
duplicating much of the code in markdown.py  and then substitutes the
parser.  Substituting the parser should be a no-no for extensions.
(Note that if several extensions do this, then one will break
another.)

Can you explain what changes you are trying to make to the parser?
Perhaps we can find a way to make the parser a little more flexible,
so that def_list extension will just need to add a hander to it,
rather than having to swap in a new parser.

- yuri

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