summaryrefslogtreecommitdiffstats
path: root/test/Java/java_version_image
diff options
context:
space:
mode:
authorMats Wichmann <mats@linux.com>2019-03-06 21:00:01 (GMT)
committerMats Wichmann <mats@linux.com>2019-03-07 20:06:04 (GMT)
commit59622eef74a5a1c698ec71cbf2d48a308c07c1fa (patch)
treea9e8fe5c8468e25d2adaf9cd43b51523b7e34174 /test/Java/java_version_image
parentf0f48202c59f8d00f47aaec25986d343e3c72ca4 (diff)
downloadSCons-59622eef74a5a1c698ec71cbf2d48a308c07c1fa.zip
SCons-59622eef74a5a1c698ec71cbf2d48a308c07c1fa.tar.gz
SCons-59622eef74a5a1c698ec71cbf2d48a308c07c1fa.tar.bz2
Clean up some file opens, regex strings
Most recent Python (3.8 alpha) spews warnings aplenty about two subjects: unclosed files and strings which look like they have embedded escapes that Python does not recognize. The latter are usually regexes, and it provides a reminder that regular expressions should normally be specified as raw strings, so Python does not attempt to interpret them. Irritating is that even docstrings are flagged, it's not obvious what the right answer is for a docstring which contains, say, a Windows-style path with backslashes. This converts a bunch of opens that are not closed into context manager usage and regex patterns into raw strings. This eliminate about 4000 warnings spewed by Py3.8 (9200 remain). Signed-off-by: Mats Wichmann <mats@linux.com>
Diffstat (limited to 'test/Java/java_version_image')
0 files changed, 0 insertions, 0 deletions