Closed
Description
TLDR:
v2.10.1 released on Nov 21st with an abundance of fixes.
v2.10.2 released on Nov 26th
v2.10.3 released on Dec 4th
v2.10.4 released on Dec 18th
We'll resume normal development (perf improvements, PR reviews, new features, etc) near the end of this week once the remaining v2.10 issues have been fixed 🚀
We've had lots of issues with url compatibility between v2.9.2 and v2.10.X, and are working to resolve these promptly.
These might be addressed, but aren't currently attached to a patch release:
-
mypy
type-checking issues affecting aField
'sdefault
value ordefault_factory
after upgrade to 2.10 #10950 - Regression using regex_engine python-re in pydantic >= 2.10b1 #11042
For v2.10.4
- Date field with year zero will raise ValueError instead of ValidationError #10967
- v2.10.x: Raises
TypeError: mro() returned a non-class ('PydanticRecursiveRef')
#11024 - Pydantic 2.10.x not installable from Azure devops due to description size #11071
- pydantic.errors.PydanticUndefinedAnnotation: name 'T' is not defined when using from __future__ import annotations with a genetic function #11076 and validate_call cannot handle parameters annotated with None #11073
- Comparison between AnyUrl objects is not working #11069
- AnyUrl: TypeError: object of type 'AnyUrl' has no len() #11092
- Include JSON Schema input core schema in function schemas #11085
For v2.10.3
- Data class with defer_build set to true causes the error AttributeError: type object '...' has no attribute '__pydantic_fields__'. Did you mean: '__pydantic_config__' #10953
- Problem generating OpenAPI schema for models with an enum as the key of a dict #10960
- Model is not fully defined together with from __future__ import annotations (Started in version 2.10.0) #11004
- 2.10:
mypy
(with pydantic.mypy) complains about Too few arguments on default factory #10945
URL issues, @sydney-runkle is working on these
- In 2.10.x AnyUrl does not validate data uris #10968
- Can't override constraints with annotations in version 2.10 #11007
- v2.10.x: OpenAPI schema generation omits constraints for HttpUrl #11019
For 2.10.2:
- Missing
eval-type-backport
as required dependency in 2.10.* Pydantic line for Python 3.8/3.9 #10958 - V2.10.1 custom model_serializer causes problems with dumping model to json #10965
- 2.10: Trouble serializing url types (as any), similar to secret types #10946
- Type of "Field" is partially unknown after v2.10 #10971
- In 2.10.1 the AnyHttpUrl is not hashable any more #10955
- Signature of "__replace__" incompatible - RootModel #10970
Handled in 2.10.1:
- 2.10:
validated_data
must be provided ifcall_default_factory
is True (affets: SQLModel) #10912 - 2.10: dataclass config issues (
arbitrary_types_allowed
, aliases, etc) #10917 - 2.10: Issue with forward annotations and serializers/
computed_field
(raises:<model> is not fully defined
) #10919 - 2.10: Type checking error on
model_fields
andmodel_computed_fields
with mypy #10907 - 2.10: URL types issues (application of constraints) #10914
- 2.10: custom
complex
serialization behavior changed? #10926 - 2.10:
HttpUrl
equality behaves differently when usingmodel_validate
vs model constructor #10932 - 2.10: Blank model title no longer respected by generated JSON schema #10935
Questions:
- 2.10: AnyHttpUrl is no longer subclass of pydantic_core.Url (according to mypy) #10920
- pydantic.networks.KafkaDsn type prohibits a valid bootstrap.servers values #10996
- 2.10: question about needing model rebuild with circular types #10925
- PostgresDsn does not accept correct postgresql:///dbname since 2.10, was accepted before #11023
- 'Url' type casts left around when serializing model to a dictionary #10998
- Numpy array alias as type regression between 2.9.2 and 2.10.0 (and later) #11000
Metadata
Assignees
Labels
No labels