Re: [Python-Dev] test_quopri is iso-latin-1 centric
This is the problem. Python source code is not in Latin-1; bytes inside strings and comments are "as-is". So the CVS "binary" mode would come closer as to how python files should be treated, although you'd still would want to convert line-endings.
Is this an "official" policy? As such I disagree with it. Either all Python source should be 7-bit clean or the source should be converted to the local convention, even for strings and comments. But if it is an official policy I'd like to hear it (who wants to channel Guido here?), because there's heaps of MacPython stuff that'll have to be converted back (I did the forward conversion a couple of months ago). As a point-in-case for local convention, you wouldn't want to be know as Martin von Lupsidedownquestionmarkwis by the chinese MacPython community or the Polish PythonWin users, would you? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
This is the problem. Python source code is not in Latin-1; bytes inside strings and comments are "as-is". So the CVS "binary" mode would come closer as to how python files should be treated, although you'd still would want to convert line-endings.
Is this an "official" policy? As such I disagree with it. Either all Python source should be 7-bit clean or the source should be converted to the local convention, even for strings and comments. But if it is an official policy I'd like to hear it (who wants to channel Guido here?), because there's heaps of MacPython stuff that'll have to be converted back (I did the forward conversion a couple of months ago).
Until we've picked a way to indicate the source encoding, it should definitely be 7-bit clean.
As a point-in-case for local convention, you wouldn't want to be know as Martin von Lupsidedownquestionmarkwis by the chinese MacPython community or the Polish PythonWin users, would you?
ROFL :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
[Martin von Lupsidedownquestionmarkwis]
This is the problem. Python source code is not in Latin-1; bytes; inside strings and comments are "as-is".
The latter is a platform-dependent accident -- the ref man says Python source is 7-bit ASCII, and that was the intent. That C's ctype functions later grew locale-dependent behavior accounts for why Python did too, but even according to the C standard you can't count on transporting C text-mode files across platforms unless they avoid that stuff.
So the CVS "binary" mode would come closer as to how python files should be treated, although you'd still would want to convert line- endings.
[Jack]
Is this an "official" policy?
My policy is that Python source in the *distribution* adheres to the restrictions of the C std for C text-mode files, until such time as Python changes to read and write them in C binary mode, or stops using C stdio altogether. And that's as official as I am <wink>.
As such I disagree with it. Either all Python source should be 7-bit clean or the source should be converted to the local convention, even for strings and comments. But if it is an official policy I'd like to hear it (who wants to channel Guido here?), because there's heaps of MacPython stuff that'll have to be converted back (I did the forward conversion a couple of months ago).
Sorry, I don't know what "forward" and "back" mean to you.
participants (3)
-
Guido van Rossum
-
Jack Jansen
-
Tim Peters