We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In #7162, "we decreed" that the Problem Code goes first, then the Correct Code
It seems that #8287 somehow reverted it? 😕
https://pylint.readthedocs.io/en/stable/user_guide/messages/warning/while-used.html (2.16.2)
https://pylint.readthedocs.io/en/latest/user_guide/messages/warning/while-used.html (2.17.0-dev0)
No response
.
The text was updated successfully, but these errors were encountered:
Perhaps
https://github.com/PyCQA/pylint/blob/899a7c595bca2936e89a87e8757c453bca687a24/doc/exts/pylint_messages.py#L87
return "\n".join((bad_code, good_code, pylintrc, details, related)) + "\n"
Sorry, something went wrong.
This is correct. Would you want to open a PR to fix it?
Successfully merging a pull request may close this issue.
Bug description
In #7162, "we decreed" that the Problem Code goes first, then the Correct Code
It seems that #8287 somehow reverted it? 😕
https://pylint.readthedocs.io/en/stable/user_guide/messages/warning/while-used.html (2.16.2)

https://pylint.readthedocs.io/en/latest/user_guide/messages/warning/while-used.html (2.17.0-dev0)

Configuration
No response
Command used
.
Pylint output
.
Expected behavior
.
Pylint version
.
OS / Environment
No response
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: