Vajrasky Kok added the comment: 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 ---------- Added file: http://bugs.python.org/file32463/better_error_message_binascii.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13637> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
