Update analytic.py: raw string invalid escape sequences #105
Conversation
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
This change fixes invalid escape sequences in strings, which produce a syntax warning on later versions of python, by making them raw strings. Incidentally, there were some `\neq` in these strings, and so this change also prevents from from being interpreted newline+eq. I didn't try hard to check that I'd caught all of these.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This change fixes invalid escape sequences in strings, which produce a syntax warning on later versions of python, by making them raw strings. Incidentally, there were some
\neqin these strings, and so this change also prevents from from being interpreted newline+eq.You can verify I haven't missed any by running a recent version of python over the file, which I have done. I haven't meticulously checked that there weren't any real escape sequences that were intended in the strings and now don't work, but given the \n thing above I think that's unlikely.