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 techtonik
Recipients amaury.forgeotdarc, docs@python, techtonik
Date 2012-12-19.15:51:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355932301.18.0.48188686616.issue16724@psf.upfronthosting.co.za>
In-reply-to
Content
In Python 2 there was no 'binary data' type - everything was a string. Now we have string, str, bytearray, array, list of ints. If hexlify is not accepting anything except bytes, it is better be explicit.

When porting code from Python 2 the argument was passed as a string with escapes inside, so it took some time to figure out why it didn't work in Py3k (actually it took a lot of time, because the research path turned wrong way at this point).
History
Date User Action Args
2012-12-19 15:51:41techtoniksetrecipients: + techtonik, amaury.forgeotdarc, docs@python
2012-12-19 15:51:41techtoniksetmessageid: <1355932301.18.0.48188686616.issue16724@psf.upfronthosting.co.za>
2012-12-19 15:51:41techtoniklinkissue16724 messages
2012-12-19 15:51:39techtonikcreate