Closed dvaccarosenna closed 1 year ago
There are breaking changes in Pydantic 1.10 which cause issues with dcutils from capturing arguments set during init. For the short term we'll add a restriction to remain on 1.9 and a separate issue will be raised to make dcutils compatible.
dcutils
Traceback (most recent call last): File "/home/user/lmctl/tests/unit/utils/dcutils/test_dc_capture.py", line 122, in test_record_pydantic_dataclass self.assertEqual(records, ( AssertionError: Tuples differ: (Attr[24 chars]_on='NOT_SET'), AttrRecord(name='second', set_[53 chars]ET')) != (Attr[24 chars]_on='ON_INIT'), AttrRecord(name='second', set_[53 chars]ET')) First differing element 0: AttrRecord(name='first', set_on='NOT_SET') AttrRecord(name='first', set_on='ON_INIT') - (AttrRecord(name='first', set_on='NOT_SET'), ? -- ^^ + (AttrRecord(name='first', set_on='ON_INIT'), ? + ^^^ - AttrRecord(name='second', set_on='NOT_SET'), ? -- ^^ + AttrRecord(name='second', set_on='ON_INIT'), ? + ^^^ AttrRecord(name='third', set_on='NOT_SET'))
Fixed by #157
There are breaking changes in Pydantic 1.10 which cause issues with
dcutils
from capturing arguments set during init. For the short term we'll add a restriction to remain on 1.9 and a separate issue will be raised to makedcutils
compatible.