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 vstinner
Recipients ncoghlan, vstinner
Date 2017-12-06.11:48:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I prefer to not talk about sys.warnoptions since, as you wrote, the order is reversed.

IMHO the priority should be (high priority > low priority):

  -W options > PYTHONWARNINGS > BytesWarning > -X dev > default filters


* BytesWarning: "ignore" by default, "default" for -b, "error" for -bb.
* default filters: 4 filters added in release mode

[('ignore', None, <class 'DeprecationWarning'>, None, 0),
 ('ignore', None, <class 'PendingDeprecationWarning'>, None, 0),
 ('ignore', None, <class 'ImportWarning'>, None, 0),
 ('ignore', None, <class 'ResourceWarning'>, None, 0)]

  or 1 filter for pydebug build:

[('default', None, <class 'ResourceWarning'>, None, 0)]

Currently, only "-W options > PYTHONWARNINGS" goes into sys.warnoptions, whereas "BytesWarning > -X dev > default filters" is added by the warnings module ("init_filters()").
Date User Action Args
2017-12-06 11:48:33vstinnersetrecipients: + vstinner, ncoghlan
2017-12-06 11:48:33vstinnersetmessageid: <>
2017-12-06 11:48:33vstinnerlinkissue32230 messages
2017-12-06 11:48:33vstinnercreate