From: dman <ds...@ri...> - 2001-11-29 00:13:46
|
On Wed, Nov 28, 2001 at 11:55:59PM +0100, Arn...@si... wrote: | > Von: dman [mailto:ds...@ri...] | > | > On Wed, Nov 28, 2001 at 07:58:47AM +0100, Humbel Otmar wrote: | > | [ Finn Bock ] | > | | > | > Non-ascii chars in identifiers? I know CPython sometimes | > | > allow that, but | > | > that is not a feature I plan on adding. | > | | > | please please NEVER even think of allowing that. Avoid special | > | characters (as Umlaute) as long as you can - they simply kill | > | developer productivity. | > | > Could you give an example? | > | > I would have thought that allowing non-english developers to use their | > native language would be nice, but I'm just a "dumb american" (if you | > know what I mean) so it really doesn't hurt me either way. | | The problem is simply: | You write some lines of code with your favourite editor, on plattform A, the | file gets stored as ascii + some local code enhancements. | Then you transfer the files to a different plattform/mashine with a | different codeset. | In the best case the names of variables, etc. changed quite dramatically in | the rest, just forget the result. Certainly if two processes try and use different encodings for the same file, it won't work. That's what happened to me with jythonc -- it was encoded in latin1 (though only a single character in a comment was affect) but jython (java) was trying to read it as utf-8. The developer's editors and environment must all be set to the correct encoding. PEP 263 addresses that as far as the interpreter is concerned. It is up to the developers to configure their editor appropriately. -D -- A)bort, R)etry, D)o it right this time |