From bd96a6f7b7eb103f97bcd6eadc21908187e94dce Mon Sep 17 00:00:00 2001 From: Mike Kaganski Date: Wed, 8 Jul 2020 11:51:48 +0300 Subject: Don't rely on Python's treatment of unrecognized escape sequences According to [1]: > Changed in version 3.6: Unrecognized escape sequences produce a DeprecationWarning. > In a future Python version they will be a SyntaxWarning and eventually a SyntaxError. [1] https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals Change-Id: Ia4f79f17ccb121f423f35b1e1306d5ae285e8762 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98321 Tested-by: Jenkins Reviewed-by: Noel Grandin Reviewed-by: Mike Kaganski --- bin/update_pch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bin/update_pch') diff --git a/bin/update_pch b/bin/update_pch index e5939e7a441c..7411e79acb80 100755 --- a/bin/update_pch +++ b/bin/update_pch @@ -581,7 +581,7 @@ def parse_makefile(groups, lines, lineno, lastif, ifstack): ingeneratedobjects = False inelse = False suffix = 'cxx' - os_cond_re = re.compile('(ifeq|ifneq)\s*\(\$\(OS\)\,(\w*)\)') + os_cond_re = re.compile(r'(ifeq|ifneq)\s*\(\$\(OS\)\,(\w*)\)') line = lines[lineno] if line.startswith('if'): -- cgit