[9.0] Move to pydantic 2 #7643
Merged
[9.0] Move to pydantic 2 #7643
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chrisburr
force-pushed
the
pydantic2
branch
3 times, most recently
from
16e7930
to
19ed3a3
Compare
fstagni
reviewed
Jun 5, 2024
fstagni
previously approved these changes
Jun 5, 2024
fstagni
approved these changes
Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This moves the pydantic models in the WMS to use pydantic 2.
Given this is only in integration I haven't bothered with supporting both pydantic 1 and 2.Actually we should support both briefly as we have a chicken-and-egg problem with diracx.BEGINRELEASENOTES
*WorkloadManagement
NEW: Support Pydantic 2
ENDRELEASENOTES