Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation warning due to invalid escape sequences #10709

Closed
3 tasks done
tirkarthi opened this issue Aug 28, 2020 · 1 comment · Fixed by #10710
Closed
3 tasks done

Deprecation warning due to invalid escape sequences #10709

tirkarthi opened this issue Aug 28, 2020 · 1 comment · Fixed by #10710
Labels
!deprecated-label:bug Deprecated label - Use #bug instead

Comments

@tirkarthi
Copy link
Contributor

Deprecation warnings are raised due to invalid escape sequences. This can be fixed by using raw strings or escaping the literals. pyupgrade also helps in automatic conversion : https://github.com/asottile/pyupgrade/ . They seemed to have been silenced in pylint but they raise deprecation warning in 3.7.0 and above.

Expected results

No warnings

Actual results

Deprecation warnings are raised

How to reproduce the bug

 find . -iname '*.py' | xargs -P4 -I{} python3.10 -Wall -m py_compile {}
./superset/models/helpers.py:49: DeprecationWarning: invalid escape sequence \]
  ",[ \t\r\n]+\]", "]", val  # pylint: disable=anomalous-backslash-in-string
./superset/config.py:149: DeprecationWarning: invalid escape sequence \e
  "\2\1thisismyscretkey\1\2\e\y\y\h"  # pylint: disable=anomalous-backslash-in-string

Environment

(please complete the following information):

  • superset version: master branch
  • python version: 3.8
  • node.js version: node -v
  • npm version: npm -v

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
@tirkarthi tirkarthi added the !deprecated-label:bug Deprecated label - Use #bug instead label Aug 28, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.90. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
!deprecated-label:bug Deprecated label - Use #bug instead
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant