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 Hunanyan, Matt.Basta, cpalmer, eric.araujo, ezio.melotti, fantoozler, fdrake, friday, georg.brandl, gsf, momat, orsenthil, r.david.murray, yotam
Date 2011-07-27.20:03:22
SpamBayes Score 8.0922764e-05
Marked as misclassified No
Message-id <1311797003.54.0.856502204583.issue670664@psf.upfronthosting.co.za>
In-reply-to
Content
IIRC we have been following what browsers do in other cases already.
There were also some discussions about supporting HTML5 (see e.g. #7311 and #11113) and the strict vs non-strict mode introduced in Python3.

Note that changing the way things are parsed is generally not backward-compatible, but you might argue that new behavior is useful enough to break some hackish code that was trying to workaround the limitations of HTMLParser.
History
Date User Action Args
2011-07-27 20:03:23ezio.melottisetrecipients: + ezio.melotti, fdrake, georg.brandl, yotam, orsenthil, fantoozler, gsf, cpalmer, eric.araujo, r.david.murray, momat, Hunanyan, friday, Matt.Basta
2011-07-27 20:03:23ezio.melottisetmessageid: <1311797003.54.0.856502204583.issue670664@psf.upfronthosting.co.za>
2011-07-27 20:03:23ezio.melottilinkissue670664 messages
2011-07-27 20:03:22ezio.melotticreate