SQLModel 0.0.14 throws mypy validation errors

[lebaudantoine]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the SQLModel documentation, with the integrated search.
• I already searched in Google "How to X in SQLModel" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to SQLModel but to Pydantic.
• I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

• I commit to help with one of those options 👆

Example Code

from typing import Optional

from sqlmodel import Field, SQLModel, create_engine

class Hero(SQLModel, table=True):
    id: Optional[int] = Field(default=None, primary_key=True)
    name: str
    secret_name: str
    age: Optional[int] = None

Description

Recent updates on SQLModel broke mypy linter.
I am using pydantic==1.10.13 and mypy==1.7.1

Linting, the following snippet of code (from the documentation) triggers two mypy errors:

...: error: Unexpected keyword argument "table" for "__init_subclass__" of "object"  [call-arg]
...: error: Metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases  [misc]

Am I doing something wrong?

Operating System

macOS

Operating System Details

No response

SQLModel Version

0.0.14

Python Version

3.12

Additional Context

No response

[kofan]

Thanks for reporting! I have the same issue with the 0.0.14 version of SQLModel. I had to roll back to the 0.0.12 version... 😔

[mohit2152sharma]

faced the same issue, downgrading works, thanks for reporting.

[hflaime]

I faced those issues, too. Upgrading to pydantic 2 resolved them for me.

[kmcentush]

Does anyone know the right way to fix this when using mypy in pre-commit hooks? I tried fiddling with additional_dependencies but couldn't get anything to work.

Or I guess we wait for a future version where it's fixed in SQLModel itself.

[JonLev]

Sorry for the extra arg 😣
The main point is the additional dependencies here, as it will include the type in the pre-commit envs

[kmcentush]

Can confirm that adding the two additional dependencies solved my problem. Thanks!

[AndrewBasem1]

@JonLev Thank you!

[menzenski]

This fixed it for me as well on sqlmodel==0.0.19. Thank you!

[jbethune]

This fixed it for me as well on sqlmodel==0.0.19. Thank you!

Can you also provide the version numbers for your other packages? Thanks!

[atlekberg]

I can confirm that this is also an issue with Pyright.

[Ben-Epstein]

I'm seeing the same with sqlmodel==0.0.18, mypy==1.10.0, pydantic==2.7.1

[muhammadyaseen]

Same issue with the following setup:

name         : pydantic                                
version      : 2.7.4

name         : sqlmodel                                                                                   
version      : 0.0.19 

name         : mypy
version       : 1.10.0

and adding additional_dependencies fixed it.

[fccoelho]

facing the same issue, and adding dependencies didn't help.
i am using pydantic 2.8.2, sqlmodel 0.0.21 and mypy 1.11.1

[juliojm13]

Using the same versions as you mention and I am facing this issue, any help?
@tiangolo

[studnikoff]

the same, please take attention to the issue
@tiangolo

[PradeepTammali]

I faced the same issue with the following versions, and adding additional_dependencies fixed it for me. I am using mypy with pre-commit.

pydantic==2.9.0
sqlmodel==0.0.22
mypy==1.11.2