Hi all! I've been trying to use Asciidoc to write blog posts, using a static site generator called Pelican. I've run into a couple of strange issues, which I've managed to hack in fixes for, but they're hacks, and the real cause, I think, is that we're calling the asciidoc api wrong somehow. But I've no idea where to start debugging.
I've documented both the issues on the pelican plugins github page, which is where the asciidoc api plugin is hosted: https://github.com/getpelican/pelican-plugins/issues/340 To repro, you should be able to do something like this: mkvirtualenv pelicanvsasciidoc pip install pelican git clone https://github.com/hjwp/pelican-plugins cd pelican-plugins git checkout b5f3852 python -m unittest asciidoc_reader.test_asciidoc_reader should fail with 2 failures saying "unexpected error: expected string or buffer". I've dug into them, and they're coming from places where asciidoc.py is encountering tuples where it was expecting strings. the subs_attrs and parse_attributes functions are involved. More info here: https://github.com/getpelican/pelican-plugins/issues/340 Any thoughts appreciated! -- ------------------------------ Harry J.W. Percival ------------------------------ Twitter: @hjwp Mobile: +44 (0) 78877 02511 Skype: harry.percival -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
