Bug(medcat): Move to new config for pydantic #169
Merged
Conversation
This file contains hidden or 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
alhendrickson
approved these changes
Oct 14, 2025
Yes, it's very much related. But it should be fixed now. Just waiting for new workflows due to the other PR using up the quota. |
tomolopolis
pushed a commit
that referenced
this pull request
Oct 15, 2025
* Update config for pydantic models - use v2-specific attribute * Add tests to make sure importing configs procudes no errors * Add more info to exception raised upon state clear * Add some more information to an error * Fix import reload during tests - run the import in a subprocess
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Move to new (pydantic 2) format for model configs.
Also added a test to make sure importing these now show no warninngs.