Re: Parser Fragility
"Sebastian Spaeth" <[email protected]> Tue, 04 May 2010 11:16:20 +0200
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
> This happens when parsing the #meta data in blog posts, I think. It > absolutely expects to find something after a "#foo " or it will break. I > think we should make pyblosxom a bit more robust, an empty #tags set for > example might be uncommon but no reason to make pyblosxom crash. OK, so lets test our new tools. Here is my proposed fix: http://gitorious.org/pyblosxom/spaetz-pyblosxom/commit/3e5e3335ba766d43115f984cc4ace7ea0930f4b4 which resolves the crash for me. All it does is use "" as #meta value if there is none given. The commit is in my clone: git clone git://gitorious.org/~spaetz/pyblosxom/spaetz-pyblosxom.git in the "robustify-parser" branch. Should I commit this to the regular master branch or do you want to pull cherry pick from here? Sebastian ------------------------------------------------------------------------------ _______________________________________________ Pyblosxom-devel mailing list Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvf5eQACgkQVYX1jMgnoGLlhwCeJi/9L6znMlLDM2z3zMgt2oBq qeUAn0zVfnXE+6zcBHlbyoK9RY7i2q6P =eTcR -----END PGP SIGNATURE-----