Pylint reports false positives on exception classes with custom init

[zhiltsov-max]

from attrs import define, field

@define(auto_exc=False, init=False)
class BaseError(Exception):
    v: int = field(default=0, kw_only=True)

    def __init__(self, msg=None, *, v=None):
        super().__init__(msg)
        self.__attrs_init__(v=v or 0)

# Pylint will raise false positive warnings for derived classes,
# when __init__ is defined directly. Monkey-patching resolves the problem:
# setattr(BaseError, '__init__', BaseError._my__init__)

@define(auto_exc=False)
class Error1(BaseError):
    x: int
    y: int

print(Error1(1, 2)) # << here

pylint pylint_example.py
************* Module pylint_example
pylint_example.py:20:6: E1121: Too many positional arguments for constructor call (too-many-function-args)

Attrs 21.4.0, pylint 2.10.2. But it happened in earlier versions too.

[hynek]

That sounds like something that should be brought up on the pylint bug tracker and not here?

[zhiltsov-max]

Ok, if you say so.

upd: it looks, there are some reports about attrs support: pylint-dev/pylint#3492 (comment)