Author ethan.furman
Recipients barry, eli.bendersky, ethan.furman, ezio.melotti, martin.panter, r.david.murray, serhiy.storchaka, veky
Date 2016-08-15.17:57:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471283831.56.0.994937394332.issue23591@psf.upfronthosting.co.za>
In-reply-to
Content
Serhiy's patch is only for IntFlags, and my patch hasn't yet fully incorporated his (many thanks for decompose!)

For IntFlags I do not expect to have very many instances alive at once, especially since not-bitwise operators will lose the IntFlag class and become plain ints.

Flags are closed.  If the zero value is not specified the repr and str are:

>>> Hah(0)
<Hah: 0>
>>> str(Hah(0))
'Hah.0'

(An RGB class might be:  <RGB.Black: 0>)

A question I have about IntFlags:

If a third-party lib specifies that certain bits are reserved and should always be zero (or at least not changed), do we want to add some easy support for that?
History
Date User Action Args
2016-08-15 17:57:11ethan.furmansetrecipients: + ethan.furman, barry, ezio.melotti, r.david.murray, eli.bendersky, martin.panter, serhiy.storchaka, veky
2016-08-15 17:57:11ethan.furmansetmessageid: <1471283831.56.0.994937394332.issue23591@psf.upfronthosting.co.za>
2016-08-15 17:57:11ethan.furmanlinkissue23591 messages
2016-08-15 17:57:11ethan.furmancreate