Defining source code encoding for Python 2.3

Jp Calderone exarkun at intarweb.us
Fri Feb 7 00:15:18 CET 2003


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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-list/attachments/20030206/c3a354a9/attachment.pgp>


More information about the Python-list mailing list