Escape backslashes in legacy research scripts (SyntaxWarning) - #76
Merged
microprediction merged 1 commit intoSep 13, 2026
Conversation
Three scripts under research/legacy_skatervaluation use non-raw string literals with invalid escapes (\d in interpretingelo.py, \g LaTeX sequences in tables.py and schurportpaperutils.py). Python 3.12+ raises `SyntaxWarning: invalid escape sequence` on import, and precise's CI matrix spans 3.9-3.13. Escaping the backslashes leaves each string's value unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014HBQNzAf5C2E3MiJC48HQw
Owner
|
thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Three scripts under
research/legacy_skatervaluation/use non-raw string literals with invalid escapes:battleutil/interpretingelo.py-\d(regex)battlelatex/tables.py-\g(LaTeX fragment in a plain string)schurcomparisonutil/schurportpaperutils.py-\g(matplotlib title)Python 3.12+ raises
SyntaxWarning: invalid escape sequencefor each.Why it matters for precise
The CI matrix spans Python 3.9-3.13; the warnings surface on import during the 3.12/3.13 jobs.
Fix
Double the backslashes so each string value is identical (ruff W605-style). None of these literals contain a valid escape, so there is no behaviour change.
Verification
ast.dumpunchanged per file;python3 -W errorpy_compile passes on all three after, failed before.🤖 Generated with Claude Code
https://claude.ai/code/session_014HBQNzAf5C2E3MiJC48HQw