-
Notifications
You must be signed in to change notification settings - Fork 27
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
Major upgrade to pydantic 2.0 #4481
Closed
22 tasks done
Comments
This was referenced Jul 18, 2023
@pcrespov explore the migration path |
This was referenced Jul 27, 2023
This was referenced Jan 15, 2024
This was
linked to
pull requests
Sep 18, 2024
20 tasks
1 task
This was referenced Oct 9, 2024
@pcrespov |
@GitHK this looks worrisome (the last ruff comment), I think the task will not run |
This was referenced Oct 29, 2024
This was referenced Nov 18, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
💀 💀 💀 Never ever squash commits when updating from master branch 💀 💀 💀
Instructions
make touch update reqs=pydantic
uv pip install bump-pydantic
bump-pydantic my_package
Planned changes
Major upgrade not out-of-the box and requires some coordination. This upgrade will bring substantial speedup to the code. It would be desirable to measure the improvement. Should we setup some type of benchmark?
Both libraries have been releases so I added a constraint in
requirements/constraints.txt
We should start testing first the upgrade with the
packages
and then when we understand the migration mechanisms we can do the rest of the repository.Tasks
This is a sub issue from ITISFoundation/osparc-issues#675
MartinKippenberger
iter_model_examples_in_module
to enable all example tests #6632pydantic-settings~=2.6
#6644The text was updated successfully, but these errors were encountered: