-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Uprev pydantic-core to 0.31.0 #5727
Conversation
ee2a972
to
4670f53
Compare
Deploying with Cloudflare Pages
|
@@ -748,7 +746,7 @@ class ComputedFieldInfo: | |||
|
|||
decorator_repr: typing.ClassVar[str] = '@computed_field' | |||
wrapped_property: property | |||
json_return_type: _core_schema.JsonReturnTypes | None | |||
return_type: type[Any] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it okay that we use Any
below but type[Any]
here? I can understand why you might do this, but just want to make sure it was intentional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My reasoning was that type[Any]
is technically incompatible if you try to assign int | str
, but internally we pretty much want to treat it as a type, so type[Any]
is more semantically meaningful
please review |
is_instance
validators w/json_or_python
validatorsRequires pydantic/pydantic-core#598 and pydantic/pydantic-core#599
All tests passing locally, will mark as ready for review once we cut the core release
Selected Reviewer: @dmontagu