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 vstinner
Recipients beazley, brotchie, vstinner
Date 2009-01-02.02:10:04
SpamBayes Score 0.0008418017
Marked as misclassified No
Message-id <>
> If the input to b64decode is a str, just do a encode('ascii')
> operation on it and proceed.  If that fails, it wasn't valid 
> Base64 to begin with.

On unicode encode error, should we raise an UnicodeEncodeError or a 

And there is also the problem of base64.b64decode() 
alternate "characters". Should we accept non-ASCII alternate 
   base64.b64decode('01a\xfeb\xffcd', altchars=b'\xfe\xff')

For the example, the result depends on the choosen charset:
 - ASCII (strict): encode input text raise an UnicodeDecodeError
 - ISO-8859-1 (ignore): works as expected
 - UTF-8 (strict): unexpected result

The only valid choice is ASCII because ISO-8859-1 or UTF-8 will 
reintroduce bytes/character mixture.
Date User Action Args
2009-01-02 02:10:06vstinnersetrecipients: + vstinner, beazley, brotchie
2009-01-02 02:10:06vstinnersetmessageid: <>
2009-01-02 02:10:05vstinnerlinkissue4769 messages
2009-01-02 02:10:04vstinnercreate