Feature or enhancement

Proposal:

Syntax warnings during AST parsing use_PyCompile_Warn to setup their warning context automatically. Though the filename is correct, the module is inferred and often not helpful. This is especially an issue when trying to ignore specific errors in a CI environment with pytest where the module is suddenlyimportlib._bootstrap. In other cases with python alone it's often justsys.

AFAICT this applies mainly to the"is" with '...' literal and'return' in 'finally' block warnings.

--
To reproduce

# test.pyclassA:def__init__(self):self.var=2deffunc(self)->bool:returnself.varis2

./python.exe -W error::SyntaxWarning:sys test.py

File"/.../test.py",line7returnself.varis2^^^^^^^^^^^^^SyntaxError:"is"with'int'literal.Didyoumean"=="?

Note: The SyntaxWarning is changed to an error for modulesys wheretest would have been the expected module.

--
The SyntaxWarning is triggered here:

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

• gh-135801: Fix inaccurate module info for SyntaxWarnings during AST parsing #135829
• gh-135801: Add the module parameter to compile() etc #139652
• gh-135801: Improve filtering by module in warn_explicit() without module argument #140151
• gh-135801: Add tests for filtering warnings by module #140240
• [3.14] gh-135801: Add tests for filtering warnings by module (GH-140240) #140246
• [3.13] gh-135801: Add tests for filtering warnings by module (GH-140240) #140247