➜

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 wiggin15
Recipients eric.araujo, mark.dickinson, martin.panter, ncoghlan, rhettinger, serhiy.storchaka, terry.reedy, wiggin15
Date 2013-09-13.13:29:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379078992.8.0.974399880253.issue9951@psf.upfronthosting.co.za>
In-reply-to
Content 
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...
History
Date User Action Args
2013-09-13 13:29:52wiggin15setrecipients: + wiggin15, rhettinger, terry.reedy, mark.dickinson, ncoghlan, eric.araujo, martin.panter, serhiy.storchaka
2013-09-13 13:29:52wiggin15setmessageid: <1379078992.8.0.974399880253.issue9951@psf.upfronthosting.co.za>
2013-09-13 13:29:52wiggin15linkissue9951 messages
2013-09-13 13:29:52wiggin15create