René's URL Explorer Experiment

Title: Align all remaining error messages with CPython by JamesClarke7283 · Pull Request #7993 · RustPython/RustPython · GitHub

Open Graph Title: Align all remaining error messages with CPython by JamesClarke7283 · Pull Request #7993 · RustPython/RustPython

X Title: Align all remaining error messages with CPython by JamesClarke7283 · Pull Request #7993 · RustPython/RustPython

Description: Summary Continues the parser error-message alignment from #7928 / #7933 / #7988. Translates many more ruff ParseErrorType variants to CPython 3.14.5's exact wording in CompileError::from_ruff_parse_error (using the source slice / parsed AST kind), plus a few codegen/symtable checks. crates/vm/src/stdlib/_ast.rs now routes its parse errors through from_ruff_parse_error, so ast.parse() / compile(..., PyCF_ONLY_AST) produce the same CPython-aligned messages as the exec path (they previously leaked raw ruff strings — and this fixes a regression where the var-param message diverged on the AST path). What's aligned aug-assign / delete / set / dict / f-string / t-string assignment targets cannot use {attribute,subscript,tuple,list,literal,function call} as import target; import X from Y → "Did you mean to use 'from ... import ...' instead?" string-prefix incompatibility ('u' and 'b' prefixes are incompatible); invalid character 'X' (U+XXXX) parenthesized def/lambda params; missing default / argument value; dict : and value syntax 'elif' block follows an 'else' block; raise from; comprehension if / unparenthesized target; ternary statement-keyword hints match case … as → cannot use {kind} as pattern target, and case … as _ → cannot use '_' as a target __debug__ as a def/class/type-param/except-handler name → cannot assign to __debug__ name 'x' is nonlocal and global; generic type-parameter wording (… cannot be used within the definition of a generic) This drops the now-passing # TODO: RUSTPYTHON; Wrong error message doctest markers and @expectedFailure decorators across test_syntax.py, test_genexps.py, test_named_expressions.py, and test_patma.py. Not covered (intentionally left marked) A few test_syntax.py cases need ruff-parser or deeper codegen changes and remain marked rather than emitting a silently-wrong message: the type-comment bare * case, class C(x for x in L) and f((x)=2) (ruff accepts these without a parse error), and dict(...); x $ y (duplicate-keyword vs lexer ordering). Runtime-error messages in unrelated subsystems (struct-sequence, format-spec, datetime, __import__, ast __replace__) are out of scope for this parser-focused change. Verification cargo clippy -p rustpython-compiler -p rustpython-codegen -- -D warnings clean; cargo fmt. Every changed message diff-tested against CPython 3.14.5 through both the exec path and ast.parse(). test_syntax test_genexps test_named_expressions test_patma test_type_params test_scope test_grammar test_compile test_exceptions all pass (961 tests). 🤖 Generated with Claude Code Summary by CodeRabbit Bug Fixes Reject the reserved identifier debug in more assignment, function/class, keyword-arg and type-parameter contexts Disallow using the wildcard _ as a capture/store target Prevent conflicting global/nonlocal declarations More CPython-aligned and clearer syntax/compile error messages; improved parse/compile error reporting and wording Chores Minor lint/implementation adjustments and a WASM import linkage hint for host imports

Open Graph Description: Summary Continues the parser error-message alignment from #7928 / #7933 / #7988. Translates many more ruff ParseErrorType variants to CPython 3.14.5's exact wording in CompileError::from_ruff_p...

X Description: Summary Continues the parser error-message alignment from #7928 / #7933 / #7988. Translates many more ruff ParseErrorType variants to CPython 3.14.5's exact wording in CompileError::from_ru...

Opengraph URL: https://github.com/RustPython/RustPython/pull/7993

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width