[issue12995] Different behaviours with <class str> between v3.1.2 and v3.2.2

[Benjamin Peterson]

Benjamin Peterson <benjamin at python.org> added the comment:

This is because how the filesystem encoding is determined has changed. You probably need to explicity discover how non-ascii characters like those in '/home/vincent/àéèîö.jpg' are encoded in your filesystem.

----------
nosy: +benjamin.peterson
resolution:  -> invalid
status: open -> closed

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