-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[ MO ] Warnings fix #5105
[ MO ] Warnings fix #5105
Conversation
Why don't you cover all files? |
It is pointless and will take a lot of time. I only covered the files, where it was necessary I disagree because it seems to me that this approach must be established on the regular basis because comments for transformations are regularly updated, new transformations along with comments are added, and other service mark symbols may affect. So your fix can be potentially broken in future. |
* warnings fix * remove redundant backslash * add whitespace in the error message
Root cause analysis: Python interprets
\
like regular expression pattern in docstring and raises a lot of warnings. So in some cases it can be difficult to read a logSolution: Declare each docstring with
\
as a row string by prependingr
before itTicket: 49765
Code:
Validation:
Documentation: