Message133096
| Author | ezio.melotti |
|---|---|
| Recipients | belopolsky, eric.araujo, ezio.melotti, fdrake, orsenthil, pluskid, python-dev, r.david.murray, v+python |
| Date | 2011-04-05.22:37:11 |
| SpamBayes Score | 6.9267276e-07 |
| Marked as misclassified | No |
| Message-id | <1302043031.89.0.372758902315.issue7311@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't see many use cases for the strict mode. It is not strict enough to be used for validation, and while parsing HTML I can't think of any other case where I would want an exception raised (always as long as what is parsed by the tolerant mode is a superset of what is parsed by the strict mode). If the parser is still able to parse what it was parsing before, I wouldn't worry too much about backward compatibility, because I can't imagine a valid use case where people would want the parser to fail (maybe someone else can?). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-04-05 22:37:11 | ezio.melotti | set | recipients: + ezio.melotti, fdrake, belopolsky, orsenthil, eric.araujo, v+python, r.david.murray, pluskid, python-dev |
| 2011-04-05 22:37:11 | ezio.melotti | set | messageid: <1302043031.89.0.372758902315.issue7311@psf.upfronthosting.co.za> |
| 2011-04-05 22:37:11 | ezio.melotti | link | issue7311 messages |
| 2011-04-05 22:37:11 | ezio.melotti | create | |