Closed reenberg closed 7 years ago
Your py2 build has failed probably because you haven't pasteurized it. That's a trick I did to panflute to support Python2, so that it can hide away most of Python2's differences from us. But then it makes the testing on Py2 most obscure.
The trick then is to rely on Travis CI. You can open an account there for free too, and you can activate Travis CI for your fork. As long as you pushes to your branch and the Travis build passes, it's good to go.
In this case I don't think we need a test on if the autofilter works. We simply follow his documentation and if it breaks that issue should be submitted to panflute.
I bumped the version and prepared a release on PyPI. Travis should push to PyPI in a few minutes. Let me know if it has problems.
Minor update to the run_filter and main function, to support running the filters automatically, as documented here: http://scorreia.com/software/panflute/guide.html#running-filters-automatically
This allows the user to add
panflute-filters
andpanflute-path
meta-data fields to the pandoc document and in turn having all of these filters run by just running pandoc as:pandoc -F panflute ...
Minor changes to the test was done, to reflect the new
doc
argument. Tests passed for py3 on my machine, but still not for py2 (as previously noted).I guess new tests should be added to demonstrate this, but I don't really know how to do this without invoking pandoc. And to be honest, I haven't worked that much with Travis/CI to know the implications of doing this. As far as I can see no other tests invoke pandoc.