RELEASED Python 2.3 (final)

sismex01 at hebmex.com sismex01 at hebmex.com
Thu Jul 31 19:21:36 CEST 2003


> From: Brian Quinlan [mailto:brian at sweetapp.com] 
> Sent: Jueves, 31 de Julio de 2003 12:17 p.m.
> 
> > Seems nice enough.  You'll only be able to assign to a 
> > mutable object anyway; 
> 
> This statement doesn't make any sense. Assignment to None is a name
> binding operating is mutability is not a relevant issue.
> 
> > None is not mutable, and will soon be a keyword.  
> 
> None becoming a keyword is a valid reason.
> 
> Cheers,
> Brian
>

Nope; it has to do with making Python faster: if constants
such as None, True, False are treated as true constants,
then certain optimizations can be enabled with help make
it all a bit quicker.

So, in order to do so, assignment to builtins is being
disallowed; or, only to such singleton instances...
I'm not too sure anymore.

Anyway, there's a thread in comp.lang.dev about all
this.

HTH

-gustavo



Advertencia:La informacion contenida en este mensaje es confidencial y
restringida, por lo tanto esta destinada unicamente para el uso de la
persona arriba indicada, se le notifica que esta prohibida la difusion de
este mensaje. Si ha recibido este mensaje por error, o si hay problemas en
la transmision, favor de comunicarse con el remitente. Gracias.





More information about the Python-list mailing list