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 serhiy.storchaka
Recipients alanmcintyre, eric.araujo, loewis, mark.dickinson, meador.inge, pleed, serhiy.storchaka, terry.reedy, ubershmekel
Date 2012-05-13.19:18:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336936838.3172.305.camel@raxxla>
In-reply-to <>
> Just add a "strict" flag, make
> it false by default, and raise an error if there is any unparsable
> extra data.

If the module does not actually checks the correctness of all
(including local file headers, which now it ignores), it will be a false
promise. And I don't understand who these checks are needed at all.

Note that the parameter "strict" in htmlparser is considered to be
Date User Action Args
2012-05-13 19:18:01serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, terry.reedy, mark.dickinson, alanmcintyre, eric.araujo, ubershmekel, meador.inge, pleed
2012-05-13 19:18:00serhiy.storchakalinkissue14315 messages
2012-05-13 19:18:00serhiy.storchakacreate