Arnon Yaari added the comment: You can follow the discussion I linked in the ticket description for an answer: http://psf.upfronthosting.co.za/roundup/tracker/issue3532 Mainly the answer is: to conform to PEP 358 and to provide the opposite of bytes.fromhex. I agree that you can use binascii, but apparently it was decided that this functionality is good to have in the builtins (what used to be encode/decode('hex') in Python 2.x, and what is now bytes.fromhex, with the missing bytes.hex). In addition, binascii works a little differently - already discussed in the given link...
---------- status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9951> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
