Hi,

I'm the author of pydoclint.

Just FYI, in pydoclint version 0.6.0 (the current latest version), this code example generates no violations:

def func1(arg1: str, arg2: int) -> int:
    """

    Args:
        arg1:
        arg2:

    Returns:
        int:

    Raises:
        ValueError:
    """
    try:
        return int(arg1) + arg2
    except:
        raise ValueError("msg")

(It has a "Returns" section in the docstring)

Here are the pydoclint config options I used:

• style: google
• argTypeHintsInDocstring: False
• skipCheckingRaises: False

So this may have been a bug only in Ruff and not in pydoclint.

There's some precedence for empty docstring rules, e.g. https://docs.astral.sh/ruff/rules/empty-docstring-section/ and https://docs.astral.sh/ruff/rules/empty-docstring/

Not really a bug, but if you omit the colon after ValueError and write something like

Raises:
    ValueError some description

then the error message is the same as if you didn't have a Raises: section at all. It would be helpful if it just said you need to add a colon.