-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
JSON output contains html-escaped characters (intentional?) #2769
Labels
Comments
It's probably not intentional, thanks for reporting the issue. |
Hey @jgsogo This is fixed, will be part of pylint 2.3.1 soon. I'm doing a pass through the regressions and will release a new bug fix release after that. |
Wow! Thanks for the quick response. 💯 |
cpitclaudel
added a commit
to cpitclaudel/pylint
that referenced
this issue
Mar 31, 2020
The JSON module already escapes special characters as needed. This was already reported in pylint-dev#2769 and partially addressed by 6b1adc6, but that commit still quotes angle brackets ('<' and '>').
cpitclaudel
added a commit
to cpitclaudel/pylint
that referenced
this issue
Mar 31, 2020
The JSON module already escapes special characters as needed. This was already reported in pylint-dev#2769 and partially addressed by 6b1adc6, but that commit still quotes angle brackets ('<' and '>').
PCManticore
pushed a commit
that referenced
this issue
Apr 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! We've just found in our CI that the JSON output has changed in
v2.3.0
, it is escaping some characters.Is it intentional, or should it be reverted to previous behavior?
Thanks!
Steps to reproduce
Run pylint on any file with an unused variable
Current behavior
Expected behavior
pylint --version output
The text was updated successfully, but these errors were encountered: