Message163337
| Author |
ezio.melotti |
| Recipients |
eric.araujo, ezio.melotti, georg.brandl, r.david.murray, serhiy.storchaka |
| Date |
2012年06月21日.14:50:12 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1340290216.51.0.465139155179.issue15114@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The attached patch include these changes:
* strict=False default
* strict arg deprecated in the doc
* strict=True deprecated (raises a warning)
* HTMLParseError deprecated in the doc
* some calls to HTMLParser.error converted to asserts [0]
Regarding
* HTMLParser.error deprecated (raises a warning)
I'm not sure anymore that's a good idea. The method is not documented, so in theory it could be removed without deprecation warnings, but that might break things if someone is using it.
[0] I made a mistake in my first message: some of the calls should actually be converted to assert, the others will stay as long as the strict mode exists (i.e. they will be removed in 3.5) |
|