Re: [Python-markdown-discuss] refactoring and treap integration

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

On Mon, Oct 13, 2008 at 4:40 AM, Yuri Takhteyev <qar...@gm...> wrote:
> I made a whole bunch of changes to the code, most of them just a
> matter of refactoring, but some affect the functionality too.
>
[snip]
> non-extension test.  But 2.0 is about as good of a chance as we will
> get for breaking backwards compatibility.
>

Wow! You were busy last night. And I agree, now is definitely the time
to make those changes.

Unless you beat me to it, I'll start working on the extensions as soon
as I can. And I'll update the writing_extensions.txt docs in the repo
once I'm confident in how everything works.

As a sidenote, I'm intrigued by the MarkdownParser class. One could
conceivably replace that class with their own which works differently
internally - as long as it has the same public methods and returns an
etree instance. This really opens up the possibility of
overriding/changing the core stuff. Cool! -- And if we want to change
the internal stuff, it should have little to no effect on the external
api.

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