Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`noqa` comments are detect as code

See original GitHub issue

This line raises an E800 warning.


# noqa: A100

These do not:


# noqa: 100
# noqa: something
# noqa: "Something"

If anything, the second block might be code (like a line of a multi-line dictionary definition). The first block is a valid noqa-comment and should not raise that warning.

Issue Analytics

State:
Created 4 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

tbrlpldcommented, Dec 9, 2019

@sobolevn Just realized I was using it wrong anyways. The # noqa: should be an inline comment anyways. When it is used that way, it is not recognized as code.

I cam across this because of the DAR docstring violations when I want to ignore these violations on a multi-line docstring. This seems to a flake8 related though. I am not sure how can you define to ignore a rule on a multi-line docstring.

0reactions

tbrlpldcommented, Dec 17, 2019

@sobolevn Thanks for pointing that out. That definitely helped.

I found a solution by utilizing the tokens that can be requested as input from flake8. See my pull request #106

Hope this is fine by you.