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 orsenthil
Recipients belopolsky, eric.araujo, ezio.melotti, fdrake, orsenthil, pluskid, python-dev, r.david.murray, v+python
Date 2011-04-06.17:27:56
SpamBayes Score 0.0004226837
Marked as misclassified No
Message-id <1302110878.44.0.778621321956.issue7311@psf.upfronthosting.co.za>
In-reply-to
Content
We need not base changes to html/parser.py on html5 spec, but rather make changes based on the requirements on parsers which may rely on this library. Like the tolerant mode was brought in issue1486713 for some practical reasons and it was seen useful tor parsers.

I don't know, how common is leaving out quotes for attributes is, but I think it can become really confusing to parsers (custom parsers). If we had not supported non-quote attributes I think, it is still okay still to not-to-support unless presented with case as very concrete bug. (like spec html 4.1 allows, which I see it does not).

The patch which added support for non-ascii characters is fine.
History
Date User Action Args
2011-04-06 17:27:58orsenthilsetrecipients: + orsenthil, fdrake, belopolsky, ezio.melotti, eric.araujo, v+python, r.david.murray, pluskid, python-dev
2011-04-06 17:27:58orsenthilsetmessageid: <1302110878.44.0.778621321956.issue7311@psf.upfronthosting.co.za>
2011-04-06 17:27:57orsenthillinkissue7311 messages
2011-04-06 17:27:56orsenthilcreate