Author ezio.melotti
Recipients eric.araujo, ezio.melotti, georg.brandl, r.david.murray
Date 2012-06-20.09:42:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340185371.41.0.609283463083.issue15114@psf.upfronthosting.co.za>
In-reply-to
Content
The deprecation plan for the strict mode of HTMLParser might be as follow:

3.3 (before the beta)
strict=False default
strict arg deprecated in the doc
strict=True deprecated (raises a warning)
HTMLParseError deprecated
HTMLParser.error deprecated (raises a warning)
calls to HTMLParser.error removed/converted to asserts

3.4
strict arg deprecated (raises a warning)

3.5
strict arg removed and strict code removed
HTMLParseError removed
HTMLParser.error removed


Everything that is parsed by strict=True is parsed by strict=False too, so changing the default shouldn't be a problem.  The difference is that strict=False won't raise any error and will parse broken markup too.  Given that no errors are raised HTMLParseError and HTMLParser.error become useless and can be deprecated (3.3) and removed (3.5) too.
Once strict=False is the default (3.3), the instances should be created simply with HTMLParser(), and eventually the strict argument will be deprecated (3.4) and removed (3.5).
History
Date User Action Args
2012-06-20 09:42:51ezio.melottisetrecipients: + ezio.melotti, georg.brandl, eric.araujo, r.david.murray
2012-06-20 09:42:51ezio.melottisetmessageid: <1340185371.41.0.609283463083.issue15114@psf.upfronthosting.co.za>
2012-06-20 09:42:50ezio.melottilinkissue15114 messages
2012-06-20 09:42:49ezio.melotticreate