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 veky
Recipients barry, eli.bendersky, ethan.furman, ezio.melotti, martin.panter, r.david.murray, serhiy.storchaka, veky
Date 2016-08-15.19:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471290335.42.0.360582641678.issue23591@psf.upfronthosting.co.za>
In-reply-to
Content
So, in fact, your Flags are simply an overlayed namespace over int (the way to give some ints sticky names), and any int is accessible from any Flags, no matter whether it has a name or not? I must say that to me it seems radically different than (Int)Enum philosophy.

    class MyIntEnum(IntEnum):
        A = 1

    >>> MyIntEnum(0)
    ValueError: 0 is not a valid MyIntEnum

So, flags are not enums, nor they share the same principles (identity, exclusiveness). Why are they in the enum module at all?
History
Date User Action Args
2016-08-15 19:45:35vekysetrecipients: + veky, barry, ezio.melotti, r.david.murray, eli.bendersky, ethan.furman, martin.panter, serhiy.storchaka
2016-08-15 19:45:35vekysetmessageid: <1471290335.42.0.360582641678.issue23591@psf.upfronthosting.co.za>
2016-08-15 19:45:35vekylinkissue23591 messages
2016-08-15 19:45:35vekycreate