[Python-Dev] xmlrpclib.{True, False} (was Re: Assignment to None) (original) (raw)
Thomas Lee tom at vector-seven.com
Sun Jun 15 15:37:25 CEST 2008
- Previous message: [Python-Dev] xmlrpclib.{True, False} (was Re: Assignment to None)
- Next message: [Python-Dev] xmlrpclib.{True, False} (was Re: Assignment to None)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benjamin Peterson wrote:
On Sun, Jun 15, 2008 at 8:11 AM, Thomas Lee <tom at vector-seven.com> wrote:
The simplest options I can think of to remedy this:
1. A setattr hack: setattr(import(name), "True", True) 2. Remove all optimization of Name("True") and Name("False") 3. Skip AST optimization entirely for the LHS of Assignment nodes (effectively removing any optimization of the "targets" tuple) You're working on optimization for the 2.6 branch, correct? In that case, why don't we take option 3 in 2.x and just reenable it in 3.x where it's completely forbidden to assign to True or False? Sorry, that's correct. This is against 2.6 trunk.
That's the idea -- in 3.x this will be a non-issue.
Cheers, T
- Previous message: [Python-Dev] xmlrpclib.{True, False} (was Re: Assignment to None)
- Next message: [Python-Dev] xmlrpclib.{True, False} (was Re: Assignment to None)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]