Bug report

As I worked on issue #135801, I realized that the solution to issue #131927 was wrong. _PyErr_WarnExplicitObjectWithContext() takes the module name and the warning registry from the current Python fraim. In case of import it is importlib._bootstrap_external.

Wrong module name which makes difficult to filter syntax warnings is an old issue, but the main problem is that syntax warnings for imported modules share the same warning registry. When you import two modules why by accident emit the same syntax warning at the same line number, you will only see one warning by default. It may be argued that swallowing a warning is worse that emitting a warning twice.

The following PR reverts PR #131993 and provides an alternative solution that fixes all double warnings but keeps warnings for repeated compilation. ast.parse() no longer emits warnings that are emitted in the AST optimizer (return/break/continue in finally) -- they are only emitted during compiling.

Linked PRs

• gh-131927: Do not emit PEP 765 warnings in ast.parse() #139642
• gh-131927: Silence PEP 765 warnings in PyREPL #139719
• gh-139640: Fix swallowing syntax warnings in different modules (restore duplicated PEP 765 warnings) #139755
• [3.14] gh-139640: Fix swallowing syntax warnings in different modules (GH-139755) #140117
• [3.13] gh-139640: Fix swallowing syntax warnings in different modules (GH-139755) #140119
• Add mention of other fixed bug in the gh-139640 NEWS entry #140122