summaryrefslogtreecommitdiffstats
path: root/Misc
diff options
context:
space:
mode:
authorMark Hammond <mhammond@skippinet.com.au>2001-05-14 03:09:36 (GMT)
committerMark Hammond <mhammond@skippinet.com.au>2001-05-14 03:09:36 (GMT)
commit2a0af79269a19b4afc423c44f8b51c22fb8ad3a3 (patch)
tree891d18deac52779ea5c4e7f7e876b0e27f0ecf31 /Misc
parenta0599575aafdd7193d7f9be05801ec9f94cac275 (diff)
downloadcpython-2a0af79269a19b4afc423c44f8b51c22fb8ad3a3.zip
cpython-2a0af79269a19b4afc423c44f8b51c22fb8ad3a3.tar.gz
cpython-2a0af79269a19b4afc423c44f8b51c22fb8ad3a3.tar.bz2
Add mention of the default file system encoding for Windows.
Diffstat (limited to 'Misc')
-rw-r--r--Misc/NEWS17
1 files changed, 17 insertions, 0 deletions
diff --git a/Misc/NEWS b/Misc/NEWS
index 3491109..aeb81c5 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -2,6 +2,23 @@ What's New in Python 2.2a0?
===========================
Core
+- Some operating systems now support the concept of a default Unicode
+ encoding for file system operations. Notably, Windows supports 'mbcs'
+ as the default. The Macintosh will also adopt this concept in the medium
+ term, altough the default encoding for that platform will be other than
+ 'mbcs'.
+ On operating system that support non-ascii filenames, it is common for
+ functions that return filenames (such as os.listdir()) to return Python
+ string objects pre-encoded using the default file system encoding for
+ the platform. As this encoding is likely to be different from Python's
+ default encoding, converting this name to a Unicode object before passing
+ it back to the Operating System would result in a Unicode error, as Python
+ would attempt to use it's default encoding (generally ASCII) rather
+ than the default encoding for the file system.
+ In general, this change simply removes surprises when working with
+ Unicode and the file system, making these operations work as
+ you expect, increasing the transparency of Unicode objects in this context.
+ See [????] for more details, including examples.
- Float (and complex) literals in source code were evaluated to full
precision only when running from a .py file; the same code loaded from a