Defining source code encoding for Python 2.3

Hello, While I rather like this new feature, I think that the current implementation is too rigour. Imagine a student that writes her first script: name = raw_input("What's your name? ") # a russian phrase here print "Hi %s!" % name With Python 2.3a1, she'll get DeprecationWarning. With a future version of Python, this code would cause SyntaxError. Does anyone really think that she must define a source code encoding here? That claim would break any possibility to use Python in schools. We have a lot of troubles with broken i18n support in IDLE and Tkinter, but this would be a total nightmare. Also defining encoding is useless here, since it affects only Unicode literals. Best regards, Kirill Simonov

On Fri, Feb 07, 2003 at 12:59:25AM +0200, Kirill Simonov wrote:
Hello,
While I rather like this new feature, I think that the current implementation is too rigour. Imagine a student that writes her first script:
name = raw_input("What's your name? ") # a russian phrase here print "Hi %s!" % name
With Python 2.3a1, she'll get DeprecationWarning. With a future version of Python, this code would cause SyntaxError.
Does anyone really think that she must define a source code encoding here? That claim would break any possibility to use Python in schools. We have a lot of troubles with broken i18n support in IDLE and Tkinter, but this would be a total nightmare.
Also defining encoding is useless here, since it affects only Unicode literals.
A gargantuan thread on this topic seems to have *just* petered out. http://groups.google.com/ will give you the whole thing, if it is already gone (unlikely!) from your local news feed. Jp -- #!/bin/bash ( LIST=(~/.netscape/sigs/*.sig) cat ${LIST[$(($RANDOM % ${#LIST[*]}))]} echo --$'\n' `uptime` ) > ~/.netscape/.signature -- up 53 days, 3:50, 4 users, load average: 0.41, 0.40, 0.33
participants (2)
-
Jp Calderone
-
Kirill Simonov