Message201972
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 |
|
Date |
User |
Action |
Args |
2013-11-02 13:43:42 | vajrasky | set | recipients:
+ vajrasky, pitrou, vstinner, luke-jr, Arfrever, r.david.murray, python-dev |
2013-11-02 13:43:42 | vajrasky | set | messageid: <1383399822.02.0.522002380045.issue13637@psf.upfronthosting.co.za> |
2013-11-02 13:43:42 | vajrasky | link | issue13637 messages |
2013-11-02 13:43:41 | vajrasky | create | |
|