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 Jim.Jewett, Michel.Leunen, ezio.melotti, georg.brandl, r.david.murray, serhiy.storchaka
Date 2012-04-13.06:20:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334298033.56.0.684135759557.issue14538@psf.upfronthosting.co.za>
In-reply-to
Content
HTMLParser is still simpler than html5lib, but if/when possible we are following the HTML5 standard rather than taking arbitrary decisions (like we used to do before HTML5).  HTMLParser doesn't claim to be a fully compliant HTML5 parser (and probably never will) -- its goal is rather being able to parse real world HTML in the same way browsers do.  There are also a couple of corner cases that are not implemented in HTMLParser because it would make the code too complicated for a little gain.
History
Date User Action Args
2012-04-13 06:20:33ezio.melottisetrecipients: + ezio.melotti, georg.brandl, r.david.murray, Jim.Jewett, serhiy.storchaka, Michel.Leunen
2012-04-13 06:20:33ezio.melottisetmessageid: <1334298033.56.0.684135759557.issue14538@psf.upfronthosting.co.za>
2012-04-13 06:20:32ezio.melottilinkissue14538 messages
2012-04-13 06:20:32ezio.melotticreate