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 taleinat
Recipients dniq, mark.dickinson, r.david.murray, serhiy.storchaka, taleinat
Date 2018-06-05.10:43:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528195389.46.0.592728768989.issue33770@psf.upfronthosting.co.za>
In-reply-to
Content
They're not the same.

When the encoded string's length modulu 4 is 2 or 3, there just need to be (at least) 2 or 1 padding characters ('=') for decoding to be successful, due to our decoder being rather strict. Less strict decoders may ignore the missing padding and successfully decode the encoded string.

When the remainder is 0, no padding is needed and everything is fine.

When the remainder is 1, the encoded string is simply invalid. It is not a padding issue. There is no valid way to decode the encoded string.
History
Date User Action Args
2018-06-05 10:43:09taleinatsetrecipients: + taleinat, mark.dickinson, r.david.murray, serhiy.storchaka, dniq
2018-06-05 10:43:09taleinatsetmessageid: <1528195389.46.0.592728768989.issue33770@psf.upfronthosting.co.za>
2018-06-05 10:43:09taleinatlinkissue33770 messages
2018-06-05 10:43:09taleinatcreate