Skip to content

tests: escape regex patterns in gc-aot runner#4984

Open
Old-Ding wants to merge 1 commit into
bytecodealliance:mainfrom
Old-Ding:codex/gc-aot-python-escapes
Open

tests: escape regex patterns in gc-aot runner#4984
Old-Ding wants to merge 1 commit into
bytecodealliance:mainfrom
Old-Ding:codex/gc-aot-python-escapes

Conversation

@Old-Ding

@Old-Ding Old-Ding commented Jul 5, 2026

Copy link
Copy Markdown

Summary

  • escape invalid Python string literal backslashes in the gc-aot test runner regex patterns
  • escape the vector argument f-string separator so Python no longer warns about \{
  • keep the parsed AST unchanged from origin/main, so the runtime strings remain the same

Verification

  • warning scan for tests/requirement-engineering/gc-aot/runtest.py reports TOTAL 0
  • AST comparison against origin/main reports AST_EQUAL True
  • python tests/requirement-engineering/gc-aot/runtest.py --help exits with 0
  • git diff --check
  • git ls-files --eol tests/requirement-engineering/gc-aot/runtest.py

I also checked for open duplicate PRs/issues mentioning invalid escape, SyntaxWarning, gc-aot, and runtest.py, and found no matches.

I did not run the full gc-aot suite because it requires the WebAssembly test toolchain/interpreter/AOT compiler setup that is not available locally.

Python 3.14 warns about invalid escape sequences in several regex and f-string literals in the gc-aot test runner. Escape those backslashes at the Python literal layer while keeping the parsed AST unchanged.

Generated-by: OpenAI Codex
Signed-off-by: aineoae86-sys <ai.neo.ae86@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants