Skip to content

gh-93343: Expand warning filter examples #106618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions Doc/library/warnings.rst
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,34 @@ Some examples::
ignore,default:::mymodule # Only report warnings triggered by "mymodule"
error:::mymodule # Convert warnings to errors in "mymodule"

.. _warning-filter-examples:

Warning Filter Examples
~~~~~~~~~~~~~~~~~~~~~~~

Here are some complex examples for filtering warnings.

Note that :func:`filterwarnings` filters have subtle differences
from :option:`-W` and :envvar:`PYTHONWARNINGS` regarding the *message* and *module*
parts of the filter (as described in :ref:`warning-filter`).

::

filterwarnings("ignore", message=".*generic", module=r"yourmodule\.submodule")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
filterwarnings("ignore", message=".*generic", module=r"yourmodule\.submodule")
filterwarnings("ignore", message="\.*generic", module="yourmodule\.submodule")

Shouldn't this be escaped as well? The r here is not necessary, and its usage should be consistent between the two args (assuming they are both regexes).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No since the first arg wants to capture strings that contain 'generic' so that the '.' catches everything, while the first arg want to capture 'yourmodule.submodule' specifically, meaning that the '.' actually captures dot and should be escaped

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it sounds to me you should put that explanation into the docs, @daniel-shimon; if it is unclear for a reviewer, it is not going to be clear for the average docs reader ;)

# Ignore warnings in "yourmodule.submodule" which contain "generic"
filterwarnings("ignore", message="generic", module=r"yourmodule\.submodule")
# Ignore warnings in "yourmodule.submodule" which START with "generic"
filterwarnings("ignore", module="yourmodule.*")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
filterwarnings("ignore", module="yourmodule.*")
filterwarnings("ignore", module="yourmodule\.*")

I think this should be escaped too.

Copy link
Contributor

@erlend-aasland erlend-aasland Jul 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, instead of using comments, would it be clearer (formatting wise) to use multiple code blocks? (Goes for the change below as well)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No because here we actually want to catch all characters after 'yourmodule' and not only dot

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# Ignore all warnings in "yourmodule" and its submodules

-W "ignore:generic::yourmodule.submodule:"
# Ignore warnings in "yourmodule.submodule" which START with "generic"
# (but not those containing it).
# Also note that the '.' in the module does not need to be escaped
# since it is not a regex.
-W "ignore:::yourmodule:"
# Ignore all warnings in "yourmodule", but NOT in its submodules


.. _default-warning-filter:

Expand Down
24 changes: 24 additions & 0 deletions Lib/test/test_warnings/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -312,6 +312,18 @@ def test_message_matching(self):
self.module.warn("something completely different")
self.assertEqual(w, [])

def test_message_matching_regex(self):
with original_warnings.catch_warnings(record=True,
module=self.module) as w:
self.module.simplefilter("ignore", UserWarning)
self.module.filterwarnings("error", ".*match", UserWarning)
self.assertRaises(UserWarning, self.module.warn, "match")
self.assertRaises(UserWarning, self.module.warn, "match prefix")
self.assertRaises(UserWarning, self.module.warn, "suffix match")
self.assertEqual(w, [])
self.module.warn("not a m4tch")
self.assertEqual(w, [])

def test_mutate_filter_list(self):
class X:
def match(self, a):
Expand Down Expand Up @@ -1202,6 +1214,18 @@ def test_single_warning(self):
PYTHONDEVMODE="")
self.assertEqual(stdout, b"['ignore::DeprecationWarning']")

def test_string_literals(self):
# Ensure message/module are treated as string literals
rc, stdout, stderr = assert_python_ok("-c",
"import sys, warnings; "
"sys.stdout.write(warnings.filters[0][1].pattern); "
"sys.stderr.write(warnings.filters[0][3].pattern)",
PYTHONWARNINGS="ignore:.generic::yourmodule.submodule",
PYTHONDEVMODE="")
self.assertEqual(stdout, rb"\.generic")
# '\Z' is added to the module name, so check start of pattern:
self.assertTrue(stderr.startswith(rb"yourmodule\.submodule"))

def test_comma_separated_warnings(self):
rc, stdout, stderr = assert_python_ok("-c",
"import sys; sys.stdout.write(str(sys.warnoptions))",
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Add examples of warning filters and the difference between programmatic and
environmental filters.
Loading