On 9/4/06, David Hopwood <[EMAIL PROTECTED]> wrote: > The issue is not simplicity of implementation; it is what will provide > the simplest usage model in the long term. If new files are encoded in X > just because most of a user's existing files are encoded in X, then how is > the user supposed to migrate to a different encoding? ...
> In practice, the system charset is often set to the charset that should > be used as a fallback *for applications that do not support Unicode*. Are you assuming that most uses of open will be for new files, *and* that these files will not also be read by such unicode-ignorant applications? Since we're only talking about text files that do not have an explicit encoding, I can barely imagine *either* of these conditions being true. -jJ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
