Jeremy Kloth <jeremy.kloth+python-trac...@gmail.com> added the comment:
Well, to really see where things are going wrong, there is always the verbose option when launching Python: py -v -c "import binascii" This will output a lot of information but should help pin down what is exactly being imported when the error occurs. If the above doesn't give enough of a clue as to the offending file, try '-vv' instead of '-v'. This increases the amount of debugging output, but does show each filename attempted for each particular import. You will need to scroll back quite awhile to get to the error location (past the cleanup messages). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue47203> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
