1 May
2013
1 May
'13
6:14 p.m.
On Wed, May 1, 2013 at 11:04 AM, Eli Bendersky
Actually, in flufl.enum, IntEnum had to define a magic __value_factory__ attribute, but in the current ref435 implementation this isn't needed, so IntEnum is just:
class IntEnum(int, Enum): ''' Class where every instance is a subclass of int. '''
So why don't we just drop IntEnum from the API and tell users they should do the above explicitly, i.e.:
class SocketFamily(int, Enum): AF_UNIX = 1 AF_INET = 2
As opposed to having an IntEnum explicitly, this just saves 2 characters (comma+space), but is more explicit (zen!) and helps us avoid the special-casing the subclass restriction implementation.
Sounds good to me. -- --Guido van Rossum (python.org/~guido)