You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pydantic released their 2.x version earlier last month, which is causing a little bit of issues when trying to use permit on projects that already use the new version, namely with fastapi.
Would it be possible to bump the requirements to update pydantic to >= 2.0? They offer an easy way to use it with the new 2.x branch, according to their docs:
The Pydantic V2 package also continues to provide access to the Pydantic V1 API by importing through pydantic.v1. For example, you can use the BaseModel class from Pydantic V1 instead of the Pydantic V2 pydantic.BaseModel class:
from pydantic.v1 import BaseModel
The text was updated successfully, but these errors were encountered:
hi @tr11, thanks for opening this issue, we are looking into a solution!
Just FYI, the suggested solution won't work because it forces the users of the permit library to upgrade pydantic to v2.
They might not be able to, because a migration might be quite difficult depending on the project.
What we'll do is either build a cross compat layer or remove pydantic altogether from this SDK.
Pydantic released their 2.x version earlier last month, which is causing a little bit of issues when trying to use permit on projects that already use the new version, namely with fastapi.
Would it be possible to bump the requirements to update pydantic to >= 2.0? They offer an easy way to use it with the new 2.x branch, according to their docs:
The Pydantic V2 package also continues to provide access to the Pydantic V1 API by importing through pydantic.v1. For example, you can use the BaseModel class from Pydantic V1 instead of the Pydantic V2 pydantic.BaseModel class:
The text was updated successfully, but these errors were encountered: