Pydantic v2 #447
Merged
Pydantic v2 #447
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
5 tasks
carrascomj
approved these changes
Oct 13, 2023
There was a problem hiding this comment.
LGTM, I think we can merge #448 into this one and merge into main.
refactor: unify some train/test code
NicholasCowie
approved these changes
Oct 13, 2023
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 change updates Maud to use pydantic version 2 and takes advantage of the new
computed_fieldfeature to remove some of Maud's awkward parsing modules.There should be no change from the user's point of view. However, this change is a necessary first step before allowing parameter values to be fixed as per #442.
Checklist: