From: Waylan L. <wa...@gm...> - 2009-01-08 16:23:53
|
On Thu, Jan 8, 2009 at 9:47 AM, Eric Abrahamsen <gi...@gm...> wrote: > > On Jan 8, 2009, at 10:10 PM, Waylan Limberg wrote: > >> Of course, there is the lxml package with various helpful html tools. >> However, being a rather difficult to install C library, we didn't want >> to make that a dependency of Python-Markdown. That said, there isn't >> any reason someone couldn't use lxml to write an extension. > > Can you give a bit of a hint in this direction – I would also much prefer to > output plain html, and I have the good fortune of having lxml installed on > my servers (ain't webfaction grand?). Lots of things are changing for > python-markdown 2.0, will the post-processors still work the same? I assume > that this currently does the trick (haven't tried it yet): > Yeah Webfaction is great. Unfortunately, not everyone offers such a great service. We had talked at one point of having markdown import lxml rather than ElementTree if it was available. Don't remember why did decided not to. The list archives would answer that. However, if you could provide a patch that works - I'll likely commit it. Now to answer your question; the extension API is fully documented [1] in the docs dir of the git repo. [1]: http://gitorious.org/projects/python-markdown/repos/mainline/blobs/8f3f5a9071631b22e41d3894c236416fef4280b7/docs/writing_extensions.txt -- ---- Waylan Limberg wa...@gm... |