Message 212605 - Python tracker

➜

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	r.david.murray
Recipients	docs@python, methane, r.david.murray
Date	2014-03-03.00:05:30
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1393805130.52.0.0457574829094.issue20837@psf.upfronthosting.co.za>
In-reply-to

Content
There are three different 'base64 alphabets' defined in the standard. The support for using them is via altchars. 'URL safe' and 'filename safe' are the two alternate alphabets defined in the standard, which you can see if you follow the link to the RFC. A patch making this more explicit in the base64 docs themselves would almost certainly be accepted.

There are three different 'base64 alphabets' defined in the standard.  The support for using them is via altchars. 'URL safe' and 'filename safe' are the two alternate alphabets defined in the standard, which you can see if you follow the link to the RFC.

A patch making this more explicit in the base64 docs themselves would almost certainly be accepted.

History
Date	User	Action	Args
2014-03-03 00:05:30	r.david.murray	set	recipients: + r.david.murray, methane, docs@python
2014-03-03 00:05:30	r.david.murray	set	messageid: <1393805130.52.0.0457574829094.issue20837@psf.upfronthosting.co.za>
2014-03-03 00:05:30	r.david.murray	link	issue20837 messages
2014-03-03 00:05:30	r.david.murray	create