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
+13 −0
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
Next Next commit
PEP 765: What's New warnings filter suggestions 
For CI use cases where static code analysis is in use,
emitting SyntaxWarnings is essentially redundant.

Accordingly, there's no harm in suggesting that folks
turn them off to avoid poor interactions between PEP 765
and treating warnings as errors.
  • Loading branch information
@ncoghlan
ncoghlan committed Oct 6, 2025
commit 5435a8a9d928b96c5731774779684f41d57331da
13 changes: 13 additions & 0 deletions Doc/whatsnew/3.14.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -937,6 +937,19 @@ The compiler now emits a :exc:`SyntaxWarning` when a :keyword:`return`,
leaving a :keyword:`finally` block.
This change is specified in :pep:`765`.

For use cases where this change is inconvenient (such as those where the
Comment thread
ncoghlan marked this conversation as resolved.
Outdated
warnings are redundant due to code linting), syntax warnings specifically
may be switched off via the :ref:`warning filter <warning-filter>`, using the
clause ``ignore::SyntaxWarning``. This can also 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``).
Comment thread
ncoghlan marked this conversation as resolved.
Outdated

Note that applying such a filter at runtime (rather than via the interpreter's
startup configuration) 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 warning.
Comment thread
ncoghlan marked this conversation as resolved.
Outdated

Comment thread
ncoghlan marked this conversation as resolved.
(Contributed by Irit Katriel in :gh:`130080`.)


Expand Down
Loading