➜

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 ethan.furman
Recipients John Belmonte, Manjusaka, ethan.furman, hauntsaninja, hroncok, jbelmonte, pablogsal, veky
Date 2021-05-26.21:16:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622063814.78.0.12509225854.issue44242@roundup.psfhosted.org>
In-reply-to
Content 
That is an intentional change.  The cause is that the masks include bits that are not named in the Flag.

The user-side fix is to add a `boundary=KEEP` option to the flag:

    class GeodIntermediateFlag(IntFlag, boundary=KEEP)

The enum library fix could be one of two things:

- automatically use the KEEP boundary when these conditions arise, and issue a DeprecationWarning; or

- lose that particular check.

I'm inclined to go with option 2, since `boundary` is designed to answer the question of what to do when Flag.A | Flag.B does not exist in Flag.
History
Date User Action Args
2021-05-26 21:16:54ethan.furmansetrecipients: + ethan.furman, jbelmonte, veky, hroncok, pablogsal, Manjusaka, John Belmonte, hauntsaninja
2021-05-26 21:16:54ethan.furmansetmessageid: <1622063814.78.0.12509225854.issue44242@roundup.psfhosted.org>
2021-05-26 21:16:54ethan.furmanlinkissue44242 messages
2021-05-26 21:16:54ethan.furmancreate