➜

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 martin.panter
Recipients Lennart Grahl, docs@python, luiz.poleto, martin.panter, steven.daprano
Date 2016-05-26.09:03:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464253393.15.0.201785871313.issue27124@psf.upfronthosting.co.za>
In-reply-to
Content 
The TypeError → binascii.Error changeover was made in revision eb45f85c4c79, to this function, along with various decoding functions in the base64 module. The base64 documenation was only slowly updated in a series of bug fixes, and it looks like unhexlify() is the only one left.

At the top of the binascii documentation, it says that the decoding functions accept ASCII strings. The general check for non-ASCII code points (raising ValueError) would be done before the specific checks for hexadecimal digits and having the right length.

Luiz’s patch looks okay to me.
History
Date User Action Args
2016-05-26 09:03:13martin.pantersetrecipients: + martin.panter, steven.daprano, docs@python, luiz.poleto, Lennart Grahl
2016-05-26 09:03:13martin.pantersetmessageid: <1464253393.15.0.201785871313.issue27124@psf.upfronthosting.co.za>
2016-05-26 09:03:13martin.panterlinkissue27124 messages
2016-05-26 09:03:12martin.pantercreate