This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients belopolsky, eric.araujo, ezio.melotti, fdrake, orsenthil, pluskid, python-dev, r.david.murray, v+python
Date 2011-04-06.16:27:21
SpamBayes Score 0.00035238906
Marked as misclassified No
Message-id <1302107242.46.0.603478474491.issue7311@psf.upfronthosting.co.za>
In-reply-to
Content
I would agree if the HTMLParser was compliant with the HTML 4.01 specs, but since it's more permissive and uses its own heuristic to determine what should be parsed and what shouldn't, I think it's better to use already existing heuristics (either the HTML5 ones or the ones used by the browsers).
I.e., I'm not trying to make it HTML5 compliant, just to make it work with what works on the browsers.
History
Date User Action Args
2011-04-06 16:27:22ezio.melottisetrecipients: + ezio.melotti, fdrake, belopolsky, orsenthil, eric.araujo, v+python, r.david.murray, pluskid, python-dev
2011-04-06 16:27:22ezio.melottisetmessageid: <1302107242.46.0.603478474491.issue7311@psf.upfronthosting.co.za>
2011-04-06 16:27:21ezio.melottilinkissue7311 messages
2011-04-06 16:27:21ezio.melotticreate