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 wiggin15
Date 2010-09-25.23:38:43
SpamBayes Score 7.655412e-06
Marked as misclassified No
Message-id <1285457928.18.0.422778723123.issue9951@psf.upfronthosting.co.za>
In-reply-to
Content
Following up on these discussions:
http://psf.upfronthosting.co.za/roundup/tracker/issue3532
http://www.gossamer-threads.com/lists/python/dev/863892

I'm submitting a patch to add bytes.hex method in accordance to PEP 358.
The code was taken from binascii so it should be "tested".
Also added bytearray.hex and fixed the documentation and testing.

There are additional things to discuss, for example:
* multiple and different implementations of tohex\fromhex - in binascii, sha1module, bytes, bytearray...
* binascii's functions which perform the same thing, but those functions and the rest of binascii's functions receive and return wrong types. I would fix this but it breaks compatibility.
History
Date User Action Args
2010-09-25 23:38:48wiggin15setrecipients: + wiggin15
2010-09-25 23:38:48wiggin15setmessageid: <1285457928.18.0.422778723123.issue9951@psf.upfronthosting.co.za>
2010-09-25 23:38:46wiggin15linkissue9951 messages
2010-09-25 23:38:45wiggin15create