# pylint: … line comments do not play well with other code analyzers (they have to appear at the end)

[posita]

Consider someone who uses Mypy notations, pyflakes, pylint, and bandit. This will confuse pylint:

… # type: … # noqa: E501 # pylint: disable=line-too-long # nosec

Pylint will give you the warning: pylint: Bad option value 'line-too-long # nosec' ("bad-option-value"). Pylint requires the line be written as follows (with the # pylint comment at the end):

… # type: … # noqa: E501 # nosec # pylint: disable=line-too-long

See also #199 and #2297.

[PCManticore]

Yes, this is 💩 . We should definitely fix it. Another separate idea is that we should add support for noqa: ERROR MESSAGE. While I was against bare noqa in the past, I think noqa: error message would help with this whole mess where every linter specifies its own pragma controls.

[PCManticore]

Should be fixed now. Please give it a go and let me know if it works for you!

[DevynCJohnson]

@PCManticore , thank you for taking the time to try to fix this issue. I had reported this issue as well - #2470 . However, I tried the code here on GitHub, but there is no change in behavior. For instance, I have a line like this some_code # noqa: N801 # pylint: disable=R0903, but Pylint will not see the its linter comment.

Although, I submitted a pull request that has the solution for #2297, #2470, and #2485.

The solution: Pull Request 2537

[PCManticore]

@DevynCJohnson Thanks but I don't think your PR actually changes anything for your linked issues. As mentioned in #2537 (comment), the current master should deal with all the linked issues, but your PR improves though a potential bug in format.py related to line-too-long and other additional linter comments.
I also have to complain about the use of try to fix the issue, please avoid it as it's quite patronising.