[issue25182] python -v crashes in nonencodable directory

[Brett Cannon]

Brett Cannon added the comment:

And what happens if you leave -v off? Since the failure is in Py_Initialize I want to know if that Py_FatalError trigger is avoided without -v.

A possible fix to test is to simply modify importlib._bootstrap._verbose_message to catch UnicodeDecodeError and then print some message saying that there was some undecodable string and just swallow the exception. I just don't know if this is in the right place to prevent Py_Initialize from erroring out.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25182>
_______________________________________