[Python-Dev] enum discussion: can someone please summarize open issues? (original) (raw)

Antoine Pitrou solipsis at pitrou.net
Sat May 4 16:25:18 CEST 2013

On Sat, 04 May 2013 06:37:23 -0700 Ethan Furman <ethan at stoneleaf.us> wrote:

>>>> >>>> +1. An enum is basically a bidirectional mapping between some raw >>>> values and some "nice" instances, so it deserves a well-defined lookup >>>> operation in each direction. >> >> As I see it, there are 3 possible ways forward here: > > 4. Offer classmethods named Enum.byname() and Enum.byvalue(). > Simple and explicit.

And then you can't have enum items named byname and byvalue.

You can. Normal shadowing rules apply.

By the same token, you can't have enum items named str or init. How is that a problem? Attribute resolution rules imply some restrictions, which are well-known to all Python programmers.

But, really, you can decide on another name if you like: byname or _byname, etc. My point is simply that lookup doesn't have to invoke operators, and explicitly named classmethods are less confusing than repurposed operators.

Regards

Antoine.

More information about the Python-Dev mailing list