Message201972
| Author |
vajrasky |
| Recipients |
Arfrever, luke-jr, pitrou, python-dev, r.david.murray, vajrasky, vstinner |
| Date |
2013年11月02日.13:43:41 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1383399822.02.0.522002380045.issue13637@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Here is another patch to better the error message. Right now, the error message when wrong input sent to unhexlify is a little bit funny.
>>> import binascii
>>> binascii.unhexlify(3)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: argument should be bytes, buffer or ASCII string, not <class 'int'>
After patch:
>>> import binascii
>>> binascii.unhexlify(3)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: argument should be bytes, buffer or ASCII string, not int |
|