> On Feb 24, 2015, at 10:56 AM, Guido van Rossum wrote:
> It sure seems that way.
Thanks for the additional feedback Guido. I’d spent some further time thinking
about what it was that I was looking for and determined it was bollocks. The
proposal was a poor solution to a specific immediate pro
On Sat, Feb 21, 2015 at 8:39 AM, Demian Brecht
wrote:
> >
> > On Feb 20, 2015, at 7:03 PM, Ian Cordasco
> wrote:
> > I hope this helps.
>
> It does, as do the other replies, thanks all. To be clear, my first gripe
> has stemmed into two related (but very minor) problems:
>
> 1. IntEnum.__str__.
>
> On Feb 20, 2015, at 7:03 PM, Ian Cordasco wrote:
> I hope this helps.
It does, as do the other replies, thanks all. To be clear, my first gripe has
stemmed into two related (but very minor) problems:
1. IntEnum.__str__. I understand the reasoning behind the current
implementation. Persona
On Fri Feb 20 2015 at 11:39:11 AM Demian Brecht
wrote:
> While working on a bug in the issue tracker, I came across something that
> I thought was a little odd around the behaviour of IntEnum. Should the
> behaviour of an instance of an IntEnum not be symmetric to an int where
> possible? For exa
While working on a bug in the issue tracker, I came across something that I
thought was a little odd around the behaviour of IntEnum. Should the behaviour
of an instance of an IntEnum not be symmetric to an int where possible? For
example:
>>> class MyEnum(IntEnum):
... FOO = 1
...
>>> MyEn
