[Edu-sig] Re: Defining source code encoding for Python 2.3

[Jp Calderone]

--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 07, 2003 at 12:59:25AM +0200, Kirill Simonov wrote:
> Hello,
>=20
> While I rather like this new feature, I think that the current
> implementation is too rigour. Imagine a student that writes her
> first script:
>=20
>     name =3D raw_input("What's your name? ") # a russian phrase here
>     print "Hi %s!" % name
>=20
> With Python 2.3a1, she'll get DeprecationWarning. With a future
> version of Python, this code would cause SyntaxError.
>=20
> 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.
>=20
> Also defining encoding is useless here, since it affects only Unicode
> literals.
>=20

  A gargantuan thread on this topic seems to have *just* petered out.=20
http://groups.google.com/ will give you the whole thing, if it is already
gone (unlikely!) from your local news feed.

  Jp

--=20
#!/bin/bash
( LIST=3D(~/.netscape/sigs/*.sig)
  cat ${LIST[$(($RANDOM % ${#LIST[*]}))]}
  echo --$'\n' `uptime` ) > ~/.netscape/.signature
--=20
 up 53 days, 3:50, 4 users, load average: 0.41, 0.40, 0.33

--xHFwDpU9dbj6ez1V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+QuyGedcO2BJA+4YRAgI2AKC9bgnkvaDGadeEUHzQEynZ/409pwCfbihQ
G8zgrGpcgIFD4pDWOTas9jg=
=A7VV
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--