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 chrysn
Recipients chrysn, docs@python
Date 2017-03-23.15:14:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490282084.27.0.505150099985.issue29886@psf.upfronthosting.co.za>
In-reply-to
Content
The function binascii.{un,}hexlify and bytes.{,to}hex do almost the same things (plus/minus details of whether they accept whitespace, and whether the hex-encoded data is accepted/returned as strings or bytes).

I think that it would help users to point that out in the documentation, eg. by adding a "Similar functionality is provided by the ... function." lines at the ends of the functions' documentations.
History
Date User Action Args
2017-03-23 15:14:44chrysnsetrecipients: + chrysn, docs@python
2017-03-23 15:14:44chrysnsetmessageid: <1490282084.27.0.505150099985.issue29886@psf.upfronthosting.co.za>
2017-03-23 15:14:44chrysnlinkissue29886 messages
2017-03-23 15:14:44chrysncreate