[Python-3000] New proposition for Python3 bytes filename issue
g.brandl at gmx.net
Tue Sep 30 20:13:49 CEST 2008
Victor Stinner schrieb:
> After reading the previous discussion, here is new proposition.
> Python 2.x and Windows are not affected by this issue. Only Python3 on POSIX
> (eg. Linux or *BSD) is affected.
> Some system are broken, but Python have to be able to open/copy/move/remove
> files with an "invalid filename".
> The issue can wait for Python 3.0.1 / 3.1.
> On Windows, we might reject bytes filenames for all file operations: open(),
> unlink(), os.path.join(), etc. (raise a TypeError or UnicodeError)
Since I've seen no objections to this yet: please no. If we offer a
"lower-level" bytes filename API, it should work for all platforms.
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.
More information about the Python-3000