Skip to content

PEP 765: specify when the SyntaxWarning will be emitted, and explain why #4132

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
iritkatriel merged 3 commits into from
Nov 21, 2024
Merged

PEP 765: specify when the SyntaxWarning will be emitted, and explain why #4132

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b62ef7a
PEP 765: specify when the SyntaxWarning will be emitted, and explain why
iritkatriel Nov 21, 2024
97cd815
typos
iritkatriel Nov 21, 2024
4e77a0c
Update pep-0765.rst
iritkatriel Nov 21, 2024
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
10 changes: 10 additions & 0 deletions peps/pep-0765.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,16 @@ However, we specify here that a ``SyntaxError`` is permitted by
the language spec, so that other Python implementations can choose
to implement that.

The CPython implementation will emit the ``SyntaxWarning`` during
``AST`` construction, to ensure that the warning will show up during
static anlaysis and compilation, but not during execution of
pre-compiled code. We expect that the warning will be seen by a
project maintainer (when they run static analysis, or CI which
does not have precompiled files). However, end users of a project
will only see a warning if they skip precompilation at installation
time, check installation time warnings, or run static analysis over
their dependencies.

Backwards Compatibility
=======================

Expand Down