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

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

> Thanks. Hey, I noticed the commits. Can y'all share more on the Wiki

Let me finish the code first.  There are still a few issues.  First,
there are a few tests that break.  Second, the Treap implementation
now requires Python 2.4.  I think we can get it to work with 2.3
without too much hassle, though.  Finally, I want to extend Treap a
little to make the initial construction of the treap a little easier.
I think the third argument to add() should be optional, defaulting to
"after the whatever is currently in the end").  I.e., I want to be
able to just write:

        self.inlinePatterns.add("escape", SimpleTextPattern(ESCAPE_RE))
        self.inlinePatterns.add("link", LinkPattern(LINK_RE))
        self.inlinePatterns.add("image_link", ImagePattern(IMAGE_LINK_RE))

> I'm surprised I've not been getting these messages in a while. I'm in
>
> the process of moving domain names, and suddenly I'm picking them up.

Well, glad you are still with us.  To make a long story shot, Artem
Yunusov did a lot of work this summer posting the code to use
ElementTree and starting the separation that I finished yesterday.
(Artem really did most of the hard work, I just took the methods,
sorted them into two classes, and then gave them simpler names.)  This
was my original goal for "2.0", which also created the opportunity to
also move to treap - only after 15 months of delay!

If you want to suggest any modifications to your treap implementation
(or other things), you can send me patches, create a "clone" on
gitorious, or email me your user name and will add you as a committer
so that you could create branches in our current repository.

- yuri

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