Type error on BaseSettings config about pydantic-settings HOT 5 CLOSED

This isn't really a solution, but a few comments for you, me and future readers ;)

I'm assuming from you usage of pylance that you're using vscode here.
Using vscode and pylance with the code above I actually don't get any of your errors.

Are you by chance using:

"python.analysis.typeCheckingMode": "strict"

?

That's the only way I get this error.

Unfortunately I have always found the strict pylance typechecking to be more annoying than helpful as it has a bunch of places where it's either overly strict or is not very supportive of pythonic code (not just in pydantic). I tend to use check types using mypy and turn pylance type checking off (or use the "basic" setting).

For example, the BaseModel has exaclty the same problem:

class FooModel(BaseModel):
    value: str

    class Config:
        title = 'foo'


class BarModel(FooModel):

    class Config:  # this will have a similar "error"
        bla = "blub"

You can of course always explicitly inherit from the parents config (like you're doing in the "fixed" version above). However, pydantics ModelMetaclass already basically does the same thing when the class is created and my assumption is that pylance can't pick up this type of "dynamic" inheritance.

from pydantic-settings.

I'm assuming from you usage of pylance that you're using vscode here. Are you by chance using: "python.analysis.typeCheckingMode": "strict"?

Yes and yes.

For example, the BaseModel has exactly the same problem:

This is incorrect, or at least not the case for me, which is why I included a BaseModel example. There are no complaints from Pylance when adding a Config to BaseModel, only when adding a Config to BaseSettings.

from pydantic-settings.

@pikeas What @daviskirk wanted to say is that you would have the same error with a second BaseModel inheriting from the first one. Internally BaseSettings inherits from BaseModel hence the same error

from pydantic-settings.

@pikeas What @daviskirk wanted to say is that you would have the same error with a second BaseModel inheriting from the first one. Internally BaseSettings inherits from BaseModel hence the same error

Thanks for clarifying, I didn't catch that initially. I think that running Pylance or MyPy in strict mode is a common use case, and worth smoothing over when possible. If Pydantic's types can be tweaked so this Just Works, that seems worth doing. Otherwise, updating the docs to use Config(ParentModel.Config)?

from pydantic-settings.

This is fixed in pydantic-settings by using SettingsConfigDict

from pydantic-settings.