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 ncoghlan
Recipients ncoghlan, vstinner
Date 2017-12-06.10:43:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When implementing the "-X dev" mode, Victor was asked to make it behave differently from "-Wd", such that "python -bb -X dev" would still raise errors for bytes comparisons.

I don't think making "-X dev" and "-Wd" inconsistent with each other is the right way to address that request. Instead, I think we should find a way to make "-bb" *always* take precedence over any supplied "-W" options.

One way to do that would be to adopt an approach similar to what I've proposed for "-X dev" in instead of making the warnings module aware of the "-bb" setting, we'd instead adjust the initialisation code to inject "error::BytesWarning" into sys.warnoptions *after* all of the entries from environment variables and the command line.
Date User Action Args
2017-12-06 10:43:15ncoghlansetrecipients: + ncoghlan, vstinner
2017-12-06 10:43:15ncoghlansetmessageid: <>
2017-12-06 10:43:15ncoghlanlinkissue32231 messages
2017-12-06 10:43:15ncoghlancreate