Coerce validator constraints to their valid type #1661
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
CodSpeed Performance ReportMerging #1661 will not alter performanceComparing Summary
|
sydney-runkle
approved these changes
Mar 4, 2025
davidhewitt
approved these changes
Mar 5, 2025
|
@davidhewitt I went and did |
|
Think that's good from me, let's wait for user reports to worry about any other cases. |
4 tasks
davidhewitt
pushed a commit
to pydantic/pydantic
that referenced
this pull request
Oct 22, 2025
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.
Change Summary
Fixes pydantic/pydantic#11341, fixes #1608.
I've applied the coercion for decimals and ints as per pydantic/pydantic#11341 (comment), should we extend to others? I'm thinking datetime types as well?
Related issue number
Checklist
pydantic-core(except for expected changes)