➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients barry, eli.bendersky, ethan.furman, gvanrossum, pitrou
Date 2016-04-13.17:50:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460569851.49.0.260709218353.issue26748@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes, I didn't find a separate bug tracker for the enum34 backport, which is why I included that version here.

> for IntEnum the behavior is correct

Do you remember the argument? I agree that IntEnum *instances* may be falsy, but IntEnum classes I don't see why.

That said, if an IntEnum *class* has to be false-y, then there's no real point in fixing just Enum (you can pass an IntEnum instance to singledispatch() too).
History
Date User Action Args
2016-04-13 17:50:51pitrousetrecipients: + pitrou, gvanrossum, barry, eli.bendersky, ethan.furman
2016-04-13 17:50:51pitrousetmessageid: <1460569851.49.0.260709218353.issue26748@psf.upfronthosting.co.za>
2016-04-13 17:50:51pitroulinkissue26748 messages
2016-04-13 17:50:51pitroucreate