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 John Belmonte
Recipients John Belmonte, Manjusaka, ethan.furman, hauntsaninja, hroncok, jbelmonte, pablogsal, veky
Date 2021-05-26.22:21:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622067672.55.0.320636551202.issue44242@roundup.psfhosted.org>
In-reply-to
Content
> Do you agree that simply removing the unnamed member check that takes place at Flag creation is a good way forward?

It's uncomfortable, because then STRICT is not actually strict, and it's going to be show raw values in str/repr.

> CONFORM -> unnamed bits are discarded (so the DEFAULT flag would be returned)

This behavior of CONFORM is a little dubious.  I expect it to conform new values after the class is constructed.  But the class members themselves should not have that transform applied, and raise an error on invalid bits.
History
Date User Action Args
2021-05-26 22:21:12John Belmontesetrecipients: + John Belmonte, jbelmonte, ethan.furman, veky, hroncok, pablogsal, Manjusaka, hauntsaninja
2021-05-26 22:21:12John Belmontesetmessageid: <1622067672.55.0.320636551202.issue44242@roundup.psfhosted.org>
2021-05-26 22:21:12John Belmontelinkissue44242 messages
2021-05-26 22:21:12John Belmontecreate