[issue34736] Confusing base64.b64decode output

Tal Einat report at bugs.python.org
Thu Sep 20 01:42:17 EDT 2018


Tal Einat <taleinat at gmail.com> added the comment:

I welcome suggestions for improvement!

We could either find a better error message covering all cases, or emit a more specific message when non-base64 characters have been skipped.

Unfortunately, skipping non-base64 characters is a basic assumption of a2b_base64 which is used under the hood, and it currently provides no indication whether such characters are skipped, and if so how many.  Also, it is common in some contexts to have line breaks in base64-encoded data, which are skipped when decoding.

----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34736>
_______________________________________


More information about the Python-bugs-list mailing list