From: Waylan L. <wa...@gm...> - 2008-08-21 20:29:44
|
On Thu, Aug 21, 2008 at 3:58 PM, Kjell Magne Fauske <kj...@gm...> wrote: > Dear Python-markdown developers, > > I have been playing with the development version of Markdown recently > and I love it. Glad to hear. > There are, however, a few bugs in the mainline version: Thanks for the reports Kjell. If you don't mind doing so, bug reports in the tracker would be helpful. That way we won't lose track of them. > > 1. Converting an empty string raises an exception: > Hmm, I thought we had addressed this before, but maybe that was `None` rather than an empty string. Anyway, this used to work before the conversion to ElementTree. Unfortunately, the current testing framework doesn't provide a way to test this one. Just another reminder that we need some UnitTests to ensure we don't break the API or this sort of thing. [snip] > > 2. The codehilite extension is broken. The code snippets are inserted > at the start of the document. This bug is triggered by markdown's test > suite, so you are probably aware of this one (the codehilite test was > uncommented in the main test file). > > 3. When converting a code block a newline and several spaces are > inserted between the <pre> and <code> tag: > After Artem updated the extensions to use ElementTree I thought a few things looked strange in the CodeHilite extension, but I haven't had a change to look closely yet. Actually, because of some recent changes to Markdown, I'm thinking that extension could be doing things a little different than it used to. It's on my todo list. -- ---- Waylan Limberg wa...@gm... |