Author Red HamsterX
Recipients Red HamsterX, ajaksu2, amaury.forgeotdarc, gvanrossum, pitrou, r.david.murray, sanxiyn
Date 2009-07-29.18:14:04
SpamBayes Score 1.10795e-08
Marked as misclassified No
Message-id <1248891245.82.0.15774886024.issue1466065@psf.upfronthosting.co.za>
In-reply-to
Content
RFC 3548, referenced by the base64 module's docs, has a rather different
statement on how invalid characters should be treated.

From 2.3 Interpretation of non-alphabet characters in encoded data:
   Implementations MUST reject the encoding if it contains characters
   outside the base alphabet when interpreting base encoded data, unless
   the specification referring to this document explicitly states
   otherwise.  Such specifications may, as MIME does, instead state that
   characters outside the base encoding alphabet should simply be
   ignored when interpreting data ("be liberal in what you accept").

So it looks like we can safely just say that invalid characters are
ignored in the docs, as long as it's explicit, but that's probably not
what people will expect.


I'll add doc patches in a moment, and someone who's actually a developer
(i.e., not me) can decide whether they're good enough.
History
Date User Action Args
2009-07-29 18:14:05Red HamsterXsetrecipients: + Red HamsterX, gvanrossum, amaury.forgeotdarc, sanxiyn, pitrou, ajaksu2, r.david.murray
2009-07-29 18:14:05Red HamsterXsetmessageid: <1248891245.82.0.15774886024.issue1466065@psf.upfronthosting.co.za>
2009-07-29 18:14:04Red HamsterXlinkissue1466065 messages
2009-07-29 18:14:04Red HamsterXcreate