Closed jameswilburlewis closed 5 months ago
This is another change in Python 3.12. The use of invalid escape sequences in string literals has been deprecated since Python 3.6, but in Python 3.12, the severity of the warning was raised, and eventually, it will no longer compile at all.
The backslashes are necessary in regular expressions (which is what the PySPEDAS usages seem to be). The standard practice is to use raw strings for regexes (e.g. r"foo.bar" rather than "foo.bar"). This is probably preferable to escaping all the backslashes (where "foo.bar" becomes "foo\\.bar"), unless, for some weird reason, you need both literal backslashes and escape sequences like \r or \n in the same string.
We have about 44 lines of code with invalid escape sequences in some of the project directories: ., -, \d, \s, etc. Maybe there are incompatibilities with regular expression syntax between IDL and Python that were lost in translation? Some of the errors in in calls to the Pandas read_csv routine, when specifying the delimiter to use.