Repository navigation
Release 4.6.0 breaks Pydantic 1.9.2 #183
Description
Our dependencies were updated to the new 4.6.0 automatically and it breaks Pydantic v1.9.2 with Python 3.9.16. The previous version 4.5.0 did not have this issue. The stack trace is listed below. Is this a legitimate issue on our end or a bug in the new release?
pydantic/main.py:205: in pydantic.main.ModelMetaclass.__new__
???
pydantic/fields.py:491: in pydantic.fields.ModelField.infer
???
pydantic/fields.py:421: in pydantic.fields.ModelField.__init__
???
pydantic/fields.py:537: in pydantic.fields.ModelField.prepare
???
pydantic/fields.py:697: in pydantic.fields.ModelField._type_analysis
???
pydantic/fields.py:781: in pydantic.fields.ModelField._create_sub_type
???
pydantic/fields.py:421: in pydantic.fields.ModelField.__init__
???
pydantic/fields.py:537: in pydantic.fields.ModelField.prepare
???
pydantic/fields.py:641: in pydantic.fields.ModelField._type_analysis
???
../.pyenv/versions/3.9.16/lib/python3.9/typing.py:852: in __subclasscheck__
return issubclass(cls, self.__origin__)
E TypeError: issubclass() arg 1 must be a class
Activity
AlexWaygood commentedon May 23, 2023
Duplicate of pydantic/pydantic#5821, #179, #180 and #182.
AlexWaygood commentedon May 23, 2023
The bug is in pydantic, and a fix has already been merged for the bug: pydantic/pydantic#5826. We're just waiting for a new pydantic release that contains the fix.
AlexWaygood commentedon May 23, 2023
pydantic v1.10.8 can now be installed from PyPI, and contains the fix.