Mark Byrne

Hi @tylerflex. From the code in the linked issue I see a problem. Here is the snipped I am referring to: ```python class ClassB(pydantic.BaseModel): """Class B""" # doesnt trigger pylint...

> inferring type from the assigned value rather than the type annotation 👍 If I use the earlier Pydantic version there are import errors: ```python x.py:2:0: E0401: Unable to import...

Pylint wasn't able to infer the `pydantic.Field` object in the **earlier** Pydantic version but it **is** able to infer it using the **latest** Pydantic version (I'm using the same latest...

There’s probably confusion here. I think it’s not specifically an issue with Pylint understanding Pydantic. I think the bigger issue is Pylint not understanding the type from the annotation. That...

I’m also referring to the discussion in the Pydantic issue linked above. I think the wrong impression was given. It’s fine to leave open, better safe than sorry.

The examples provided in the previous two comments won't emit `no-member` if the `pylint-pydantic` plugin is used: `pylint --load-plugins pylint_pydantic example.py`. The original `v1` example still emits the message, however;...

@evelyn-ys in that example, moving the disable will have the desired outcome: ```patch -def load_arguments(self, _): # pylint: disable=too-many-statements, too-many-locals +def load_arguments(self, _): + # pylint: disable=too-many-statements, too-many-locals ``` With...

@bebound I think there are some side-effects with the various disables that are currently in the module - there seems to be a bug there somewhere. When I remove all...

Thanks @emontnemery for the report. I can reproduce this using the example over in the sqlalchemy issue (copy/paste below). The example in the description doesn't run successfully as a Python...

> > The example in the description doesn't run successfully as a Python script however. > > Sorry, I did not know that was a requirement. Should I edit the...