> > What would you expect a Pythonic enum to look like?
> >
> > class Colour(Enum):
> > red
> > green
>
> Hell no. I mean, even Go isn't that implicit, you still have to use the iota there.
No, Go just provides plain boring wannabe enums.
Pascal(1972), Modula-2(1978), Ada(1983), and many others:
type Color = (red, green)
ord(red) = 1, ord(green) = 2
len(Color) = 2
succ(red) = green
pred(green) = red
red < green
type colors = array [Color] of int;Almost any starting special character would be good enough to make it explicit:
class Colour(Enum):
* red
* green
* blue
* none, transparent, emptyLooks like a hybrid of Python and Markdown. And I think such thing deserves to exist!
class Color(Enum):
red, green, blue, *_ = range(2**128)
red_alias = red
Does that create a list of size 2^128-3 = 340282366920938463463374607431768211453 and assign it to Color._?
Re:Python's sad, unimaginative Enum
by lclarkmichalek on Saturday May 11, 2013 @06:18PM
(#5692316)
Ha! Too much Go for me. It does actually, my bad, I expected the variable to be ignored (and the range creation isn't a big deal usually as it's just a generator).
Using range would create the whole list. xrange is the one that acts like a generator :)
This Enum is slated to be introduced in Python 3.4, where range is (not acts like) a generator.
Ah. I stand corrected :)
But even with a generator, as you would get from range in Python 3, the assignment
a, *b = range(10)
makes b into a list. (And I think the star syntax in assignments is only Python 3, as far as I remember Python 2 only has star in argument lists of functions.)You're right, python2 doesn't have the extended unpacking (star) syntax. Furthermore, this:
>>> a, *b = range(2**128)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OverflowError: Python int too large to convert to C ssize_t
Ha.Yes it does and that is because it actually assigns all of the rest to a variable named '_'. The use of the underscore as a throwaway variable is just a convention and the interpreter is not aware that the result should be ignored.
And if you do actually want to prevent the duplication problem, you can do this
Or alternatively, if having to specify how many values is too unimaginative for you, something like will also work. It's true! IDEs don't deal well with meta-programming, and Python isn't Lisp! I don't love the namedtuple syntax particularly either, but what solution would you propose? There doesn't seem to be an easy way around it, afaict. Well, if we read the PEP (http://www.python.org/dev/peps/pep-0435/#id26): We see that printing an enum value gives the string representation, so I don't really think that it not defaulting to strings is that much of a problem. I think I almost agree with you here. That said, zero does have a specific meaning in a boolean context, so I can see why they didn't go for it. Aside from the whole never going to happen argument, I think this kind of shows the problem with doing this implicitly; whatever you do, it's not going to work for some people. Hey, don't despair so much. You can always read the PEP and realise you can actually provide a dictionary as the second argument. So maybe you'd prefer to have your enums start from 0. I should mention, this information is in the PEP: http://www.python.org/dev/peps/pep-0435/#id35