-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to Pydantic v2 #180
Comments
Any thoughts @surchs? I've started making some of the necessary changes (based on currently failing tests) in a branch and think the migration shouldn't require any major rewrites on our end, but some of the updates related to deprecated methods would probably benefit from a closer look as they involve a bit of extra code to preserve existing behavior. |
Bumping this up since my ill advised late night commit (1d4cb52) to main has made this an actual blocker. |
Will pin pydantic version for now. Taking this issue off of backlog in favour of #184. |
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
|
🚀 Issue was released in |
The release of Pydantic V2 introduced several breaking changes in the code due to name changes of multiple methods, removed or deprecated types/methods/objects, and broader changes to the logic of fields, validators, + more.
The docs for V2 have not quite caught up to the changes yet, but there is a comprehensive migration guide 🎉
PydanticUserErrors
Related are:
#179
TODO:
The text was updated successfully, but these errors were encountered: