➜

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.21:59:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622066366.37.0.665130597956.issue44242@roundup.psfhosted.org>
In-reply-to
Content 
> However, if the user is interfacing with other software/hardware, they may not have a choice on which bits make up the mask.

I think it's the same as saying "unknown bits may come on the input".  An important use case is for forward compatibility, where new bits may be added but you don't want to break existing code.

That is what CONFORM is for.  The cited code should either declare the masks as I've shown if STRICT is desired, or use CONFORM if forward compatibility is desired.
History
Date User Action Args
2021-05-26 21:59:26John Belmontesetrecipients: + John Belmonte, jbelmonte, ethan.furman, veky, hroncok, pablogsal, Manjusaka, hauntsaninja
2021-05-26 21:59:26John Belmontesetmessageid: <1622066366.37.0.665130597956.issue44242@roundup.psfhosted.org>
2021-05-26 21:59:26John Belmontelinkissue44242 messages
2021-05-26 21:59:26John Belmontecreate