Removing the '\s' warnings from regexps#23
Merged
gtribello merged 1 commit intoplumed:mainfrom Oct 27, 2025
Merged
Conversation
Iximiel
force-pushed
the
warning/invalid-escape-sequence
branch
from
d1a6b2a to
2a2d56c
Compare
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.
As title, this is tiny, but removes a lot of noise when the interpreter passes onto the non raw strings where the regexp are defined.
On my computer gives also less errors in building the manual, even if I do not think it is a priority to push this as a new version