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 ezio.melotti
Recipients Neil Muller, ezio.melotti, fdrake, jjlee, kxroberto, orsenthil, r.david.murray, terry.reedy
Date 2011-11-16.08:28:56
SpamBayes Score 5.190392e-08
Marked as misclassified No
Message-id <1321432136.8.0.865869582555.issue1486713@psf.upfronthosting.co.za>
In-reply-to
Content
The strict/tolerant mode mainly works by using either a strict or a tolerant regex.  If the markup is invalid, the strict regex doesn't match and it gives an error.  The tolerant regex will match both valid and invalid markup at the same time, without distinctions, and that's why there's no way to emit a warning for these cases.  I think there are a couple of places where a warning could be emitted, but that would just cover a small percentage of the errors.  Even if we find a way to emit a warning for everything allowed by the tolerant mode that fails on strict, it won't still cover all the possible errors, that's why I think tools like validators and conformance checkers (or even the warning/error logs) should be used instead.
History
Date User Action Args
2011-11-16 08:28:56ezio.melottisetrecipients: + ezio.melotti, fdrake, terry.reedy, jjlee, orsenthil, kxroberto, Neil Muller, r.david.murray
2011-11-16 08:28:56ezio.melottisetmessageid: <1321432136.8.0.865869582555.issue1486713@psf.upfronthosting.co.za>
2011-11-16 08:28:56ezio.melottilinkissue1486713 messages
2011-11-16 08:28:56ezio.melotticreate