Dāvis added the comment: it makes no sense to not use better encoding default in some cases like my patch does. Most programs use console's encoding not ANSI codepage and thus by limiting default only to ANSI codepage we force basically everyone to always specify encoding. This is current behavior that ANSI codepage is used and that's why this issue and also #27048. if we keep it this way then specifying encoding will be required for like 99% of cases which means it's useless default. Actually I don't even know any Windows program which does input/output (not talking about files because that's different) in ANSI codepage because it would be broken when displayed in console as that by default uses OEM codepage. Anyway my patch doesn't really change default it just uses console encoding in most cases and then fallbacks to same current default ANSI codepage.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27179> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
