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 r.david.murray
Recipients barry, jesstess, pitrou, r.david.murray, zvyn
Date 2014-06-12.21:43:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Correction on the XXX should we check this: I was thinking about the wrong section of the code.  But it is still 'no': by postel's law we should accept dirty data.  Currently the consumer of the library can then decide whether or not to reject the dirty data by building a subclass.  It might be nice to provide an option to control rejection of invalid characters in commands, but that should be a separate issue.  (And, we are ending up with so many options that we might want to think about whether or not there is a better API for controlling them).
Date User Action Args
2014-06-12 21:43:41r.david.murraysetrecipients: + r.david.murray, barry, pitrou, jesstess, zvyn
2014-06-12 21:43:41r.david.murraysetmessageid: <>
2014-06-12 21:43:41r.david.murraylinkissue21725 messages
2014-06-12 21:43:40r.david.murraycreate