userspace: eliminate warning in process_gperf.py #11963
Merged
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
Python 3.7 throws a FutureWarning when it thinks it has found a nested set in a regular expression. We weren't actually; just trying to match some brackets. Escape them instead. No functional difference. Fixes: zephyrproject-rtos#11961 Signed-off-by: Andrew Boie <[email protected]>
nashif
approved these changes
Dec 8, 2018
Codecov Report
@@ Coverage Diff @@
## master #11963 +/- ##
=======================================
Coverage 48.17% 48.17%
=======================================
Files 281 281
Lines 43360 43360
Branches 10392 10392
=======================================
Hits 20887 20887
Misses 18318 18318
Partials 4155 4155Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Python 3.7 throws a FutureWarning when it thinks it
has found a nested set in a regular expression.
We weren't actually; just trying to match some brackets.
Escape them instead. No functional difference.
Fixes: #11961
Signed-off-by: Andrew Boie [email protected]