Re: [Python-markdown-discuss] second Markdown() instance clobbers the first?

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

On Sat, Oct 4, 2008 at 3:12 PM, Yuri Takhteyev <qar...@gm...> wrote:
>
> I think we have two options: we can either make all the patterns
> stateless, and give them an instance of Markdown() if they want to
> look up config parameters.  Or we could give each instance of Markdown
> it's own set of patterns.  I am leaning on the second solution, but
> note the downside: the we are relying on those variables in the
> extensions, so this would break many of the extensions.  If we'll be
> doing this, we might as well make the effort now to add a treap for
> ordering the preprocessor, as Ben Wilson suggested last year.
>
[snip]
>
> What do you guys think?
>

I agree. I'm leaning toward the second option as well. Btw, Ben must
have failed to copy the list on the last few emails he sent you
because last I knew we was still working on it. Yet, a few times since
then, you've made some comments that seem to indicate you saw some
code of his.

In any event, if we are going to do anything link this, it should
definitely be before we release 2.0. The move to ET already broke
existing extensions and seeing we havn't released since then, we might
as well keep going with the changes. I suspect most people are still
using 1.7 with any private extensions they've written so they'll have
to update witht he next release anyway.

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