summaryrefslogtreecommitdiffstats
path: root/CryptoPkg
diff options
context:
space:
mode:
authorMike Beaton <mjsbeaton@gmail.com>2024-09-18 16:40:08 +0100
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2024-09-23 04:55:53 +0000
commit6820004b3e2b6997b8ad8663c548fb3da2fcb3b2 (patch)
tree92c668c9b72fd25bf5aa4b1dd09a7fcabb485c43 /CryptoPkg
parent0354e89fc94b85148eded1b1ad7d1f626afdae04 (diff)
downloadedk2-6820004b3e2b6997b8ad8663c548fb3da2fcb3b2.tar.gz
edk2-6820004b3e2b6997b8ad8663c548fb3da2fcb3b2.tar.bz2
edk2-6820004b3e2b6997b8ad8663c548fb3da2fcb3b2.zip
BaseTools: Fix multiple 'invalid escape sequence' warnings in tests
In Python 3.12 invalid escape sequences in strings moved from DeprecationWarning to SyntaxWarning (ref https://docs.python.org/3/whatsnew/changelog.html#python-3-12-0-final and search for gh-98401). In a future Python version this will become SyntaxError. Multiple instances of these SyntaxWarnings are currently printed when running the BaseTools tests using Python 3.12 (though without actually failing the affected tests). This commit updates all lines which were causing this type of warning. Typical examples which needed fixing are: - "BaseTools\Source\Python" representing a path: "\S" and "\P" are invalid escape sequences, therefore left unchanged, therefore the test works (with a warning in Python 3.12). r"BaseTools\Source\Python" represents the same string, but with escapes turned off completely thus no warning. - Where '\t\s' is used as a regex pattern, then chr(9) + '\\s' is sent to the regex parser (with a warning in Python 3.12) since '\s' is not a valid Python escape sequence. This works correctly, though arguably for the wrong reasons. r'\t\s' sends the same as '\\t\\s', as originally intended and with no warning. (Note that ' and " are not fundamentally different in Python.) Signed-off-by: Mike Beaton <mjsbeaton@gmail.com>
Diffstat (limited to 'CryptoPkg')
0 files changed, 0 insertions, 0 deletions