[Python-Dev] enum discussion: can someone please summarize open issues?
Greg Ewing
greg.ewing at canterbury.ac.nz
Fri May 3 15:34:59 CEST 2013
More information about the Python-Dev mailing list
Fri May 3 15:34:59 CEST 2013
- Previous message: [Python-Dev] enum discussion: can someone please summarize open issues?
- Next message: [Python-Dev] enum discussion: can someone please summarize open issues?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Barry Warsaw wrote: > I still don't get it why this is an issue though, or at least why this is > different than any other getattr on any other class, It's not a problem that getattr() has this behaviour. What I'm questioning is the idea that getattr() should be the only provided way of doing a name->enum lookup, because that will require everyone to do extra checks to ensure safety. -- Greg
- Previous message: [Python-Dev] enum discussion: can someone please summarize open issues?
- Next message: [Python-Dev] enum discussion: can someone please summarize open issues?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list