anatoly techtonik added the comment:
The fact that array.array, bytearray and memoryview are also accepted is a
surprise for me. It will help if Python docs contained a definition of what can
be considered 'binary data' and link this term from hexlify description to this
definition.
Amaury Forgeot d'Arc added the comment:
Isn't such a definition already present in the top-level paragraphs?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16724
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: -serhiy.storchaka
versions: -Python 3.1, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16724
___
Chris Jerdonek added the comment:
It will help if Python docs contained a definition of what can be considered
'binary data' and link this term from hexlify description to this definition.
I believe this is part of the goal of issue 16518, where bytes-like object is
being proposed as one of
Raymond Hettinger added the comment:
I concur with Amaury and Andrew. The docs are fine as-is.
--
nosy: +rhettinger
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16724
