[docs] [issue1753718] base64 "legacy" functions violate RFC 3548

R. David Murray report at bugs.python.org
Sun Dec 13 19:40:47 EST 2015


R. David Murray added the comment:

I started tweaking this patch, and wound up going through the whole doc and fixing the references to 'byte string' and 'string' throughout, as well as making all the entries consistent in how they reference the function arguments and output (previously some did not reference the output at all, nor was it clear that the output is always bytes).  I believe I also clarified some confusing wordings along the way.

Since there are so many changes I need some eyes checking my work before I commit.

Note that the primary motivation for this change (the incorrect claim that both interfaces supported the RFC) is not made by the 2.7 docs, and since those docs are very different now, I don't plan to touch them.

----------
stage:  -> patch review
Added file: http://bugs.python.org/file41296/issue-01753718.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1753718>
_______________________________________


More information about the docs mailing list