Skip to content

PEP 765: What's New warnings filter suggestions #139658

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.

Sign up for GitHub

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

Merged
AA-Turner merged 3 commits into from
Oct 6, 2025
Merged

PEP 765: What's New warnings filter suggestions #139658

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5435a8a
PEP 765: What's New warnings filter suggestions
ncoghlan Oct 6, 2025
9db5c40
Apply suggestions from code review
ncoghlan Oct 6, 2025
9b1ae08
Tweak code review suggestions
ncoghlan Oct 6, 2025
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
Prev Previous commit
Tweak code review suggestions
  • Loading branch information
@ncoghlan
ncoghlan authored Oct 6, 2025
commit 9b1ae088967f93fa25860907e717b0caf3b4c26f
6 changes: 3 additions & 3 deletions Doc/whatsnew/3.14.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -939,13 +939,13 @@ This change is specified in :pep:`765`.

In situations where this change is inconvenient (such as those where the
warnings are redundant due to code linting), the :ref:`warning filter
<warning-filter>` can be used to turn off all syntax warnings, by using the
``ignore::SyntaxWarning`` filter. This can be specified in combination
<warning-filter>` can be used to turn off all syntax warnings by adding
``ignore::SyntaxWarning`` as a filter. This can be specified in combination
with a filter that converts other warnings to errors (for example, passing
``-Werror -Wignore::SyntaxWarning`` as CLI options, or setting
``PYTHONWARNINGS=error,ignore::SyntaxWarning``).

Note that applying such a filter at runtime, using the :mod:`warnings` module
Note that applying such a filter at runtime using the :mod:`warnings` module
will only suppress the warning in code that is compiled *after* the filter is
adjusted. Code that is compiled prior to the filter adjustment (for example,
when a module is imported) will still emit the syntax warning.
Expand Down
Loading