Disable --ignore-noqa for specific rule in CLI

[97gamjak]

So my problem is basically that I really don't want any developer/contributor of my package make unnecessary use of the #noqa inline feature. However, we encountered one false positive, for which we could not find a workaround.

Therefore, we would ask if it is possible to call ruff check --ignore-noqa but keep the #noqa for one specific rule?

[MichaReiser]

I haven't tested it but https://docs.astral.sh/ruff/settings/#lint_external might work for your use case.

[97gamjak]

That actual looks really promising 👍. I'll give it a try later today. Thank you

[97gamjak]

If anyone stumbles across this discussion: Just FYI i did not try this approach - my final solution can be found in this comment

[MichaReiser]

Or you might be able to ignore that the one rule where you want noqa comments to be allowed when checking with --ignore-noqa

[97gamjak]

If I get your idea right, this is not really an easy solution for us. This special #noqa can be found in several places inside the code, but it is always the same linting issue. To be more precise to ruff it seems that a runtime import can be placed inside the type checking box rule-TC002, but it can't. And we really don't want to disable this (IMO) useful rule globally.

maybe there would also be a workaround directly inside the code?

import pandas as pd
from pydantic import BaseModel

class Foo(BaseModel):
    foo_data: pd.DataFrame
    
    class Config:
        arbitrary_types_allowed = True

here ruff triggers for pd but importing it only for type checking makes pydantic break.

[MichaReiser]

Can you try the following configuration:

[tool.ruff.lint.flake8-type-checking]
runtime-evaluated-base-classes = ["pydantic.BaseModel"]

See https://docs.astral.sh/ruff/settings/#lint_flake8-type-checking_runtime-evaluated-base-classes

[97gamjak]

yes! that did the trick!

Thank you very much I must have missed this setting