[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by miss-islington : -- pull_requests: +10573, 10574 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by miss-islington : -- pull_requests: +10573, 10574, 10575 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by miss-islington : -- pull_requests: +10573 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by Raymond Hettinger : -- pull_requests: +10570, 10571 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by Raymond Hettinger : -- pull_requests: +10570 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Change by Raymond Hettinger : -- pull_requests: +10570, 10571, 10572 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Raymond Hettinger added the comment: This is a reasonable suggestion. Will apply the patch shortly. -- nosy: +rhettinger resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

Changes by Roundup Robot : -- pull_requests: +689 ___ Python tracker ___

[issue29886] links between binascii.{un,}hexlify / bytes.{,to}hex

New submission from chrysn: 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