Nick Coghlan added the comment: Think sysadmins running scripts on Linux, writing to the console or a pipe. I agree the generalisation is a bad idea, so only consider the original proposal that was specifically limited to the standard streams.
Specifically, if a system is properly configured to use UTF-8 for all interfaces, I shouldn't have to live in fear of Python steps in a command pipeline falling over because it happens to encounter a filename encoded with latin-1 (etc). If the bytes oriented os tools like ls don't fall over on it, then neither should Python. This is about treating the standard streams as OS interfaces, as long as they're using the filesystem encoding. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18713> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
