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 martin.panter
Recipients Julian, docs@python, martin.panter, python-dev, r.david.murray, terry.reedy
Date 2015-12-14.05:44:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450071884.98.0.899622180719.issue22088@psf.upfronthosting.co.za>
In-reply-to
Content
While porting the Python 3 changes over, I noticed some related problems in the Python 2 and 3 documentation:

* Due to the internal alphabet translation, characters that are in the original base-64 alphabet (+ and /) are not discarded, even if an alternative alphabet is specified
* Doc strings of standard_ and urlsafe_b64decode() need fixing as well
* Found some copy-paste errors in the doc strings
* There are only two distinct base-64 alphabets defined by the RFCs, not three. The URL-safe alphabet and the filename-safe alphabet are the same thing.

Here is a patch for review. I will hold off on this until Issue 1753718 has been sorted out to avoid conflicts in the Python 3 docs.
History
Date User Action Args
2015-12-14 05:44:45martin.pantersetrecipients: + martin.panter, terry.reedy, r.david.murray, docs@python, Julian, python-dev
2015-12-14 05:44:44martin.pantersetmessageid: <1450071884.98.0.899622180719.issue22088@psf.upfronthosting.co.za>
2015-12-14 05:44:44martin.panterlinkissue22088 messages
2015-12-14 05:44:44martin.pantercreate