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 mouse07410
Recipients docs@python, martin.panter, matrixise, mouse07410, r.david.murray
Date 2015-10-30.16:29:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446222548.62.0.494818619484.issue25495@psf.upfronthosting.co.za>
In-reply-to
Content
As far as I remember, the data was not "originally processed in 57-byte chunks". I've been around the first PEM and MIME standards and discussions (and code, though not in Python, which wasn't around then) to be in position to know. :)

Whether the user prefers to process data in chunks or not, is up to the user. 
Not to mention that PEM is long gone, and MIME also changed somewhat. 

The link between this function and RFC4648 can and should be more explicit, but I think just referring to it is enough. 

Do you have a recommendation for additional info to explain newline issues?

Yes, changing "Base64 output" to "function output" makes perfect sense.

Thanks!
History
Date User Action Args
2015-10-30 16:29:08mouse07410setrecipients: + mouse07410, r.david.murray, docs@python, martin.panter, matrixise
2015-10-30 16:29:08mouse07410setmessageid: <1446222548.62.0.494818619484.issue25495@psf.upfronthosting.co.za>
2015-10-30 16:29:08mouse07410linkissue25495 messages
2015-10-30 16:29:08mouse07410create