Roundup Robot added the comment:
New changeset 105bf5dd93b8 by R David Murray in branch '3.5':
#1753718: clarify RFC compliance and bytes/string argument types.
https://hg.python.org/cpython/rev/105bf5dd93b8
--
nosy: +python-dev
___
Python tracker
R. David Murray added the comment:
Everything here should be covered by the fix committed for #1753718. If I
missed anything let me know :)
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
R. David Murray added the comment:
Darn. I *thought* I remembered there being an existing patch for this when I
was working on that other issue, but I couldn't find it.
--
___
Python tracker
Martin Panter added the comment:
Hopefully the patch proposed for Issue 1753718 will address this issue. Many of
my comments there would also apply to the patch here.
--
dependencies: +base64 "legacy" functions violate RFC 3548
nosy: +martin.panter
stage: needs patch -> patch review
Milan Oberkirch added the comment:
changed 'bytes' and 'byte string' to `bytes-like object` and reviewed usage of
'byte' and 'string' (the letter made sense to me at some points, e.g. something
like ... altchar is a string with two or less letters ...).
--
keywords: +patch
nosy:
New submission from R. David Murray:
The base64 documentation (http://docs.python.org/3/library/base64.html) does
not use the new python3 byte/string terminology consistently (sometimes not
even within the same paragraph).
--
assignee: docs@python
components: Documentation
messages: