On Thu, 2010-01-21 at 22:21 +0100, "Martin v. Löwis" wrote: > > Where the default *file system encoding* is used (i.e. text files are > > written or read without specifying an encoding) > > I think you misunderstand the notion of the *file system encoding*. > It is *not* a "file encoding", but the file *system* encoding, i.e. > the encoding for file *names*, not for file *content*. > > It was used on Windows for Windows 95; it is not used anymore on Windows > (although it's still used on Unix). > > I think there are way too many specific cases where Python 3 will encode > implicitly to get a complete list from the memory. If you really are > after a complete list, you'll need to perform a thorough code review. > For a few examples where some kind of default encoding is applied, > consider XML and the dbm interfaces.
Thanks for the clarification. To add to the "fun", libraries accessed via wrapper modules may have their own ideas about filename encodings as well. For example, GTK's GLib library uses environment variables G_FILENAME_ENCODING and G_BROKEN_FILENAMES to when converting between strings and OS calls [1]. Dave [1] http://library.gnome.org/devel/glib/stable/glib-running.html _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
