-
Notifications
You must be signed in to change notification settings - Fork 265
Tightening of pydantic dependancy following release of v0.11.1 #869
Comments
Appreciate the stance outlined here. We don't use pydantic in our service and it feels peculiar for us to restrict a transitive dependency, but that may be my misunderstanding. |
https://github.com/datafold/data-diff/blob/master/data_diff/dbt_config_validators.py#L3
|
Experiencing the exact same issue. Can confirm data-diff 0.11.1 with the redshift extra is broken. |
Same issue here (now with data-diff 0.11.1 and the snowflake extra). Adding |
Yeah I would argue its annoying for me to have to restrict a transitive dependancy, so hoping we can restrict within this package. |
This issue has been marked as stale because it has been open for 60 days with no activity. If you would like the issue to remain open, please comment on the issue and it will be added to the triage queue. Otherwise, it will be closed in 7 days. |
Hi @FChmiel et al, I'm sorry for the delay in responding. Thank you for trying out data-diff and for opening this issue! We made a hard decision to sunset the data-diff package and won't provide further development or support. Diffing functionality will continue to be available in Datafold Cloud. Feel free to take it for a trial or contact us at [email protected] if you have any questions. -Gleb |
Describe the bug
The recent release changed the dependency of pydantic from "1.10.12" to ">=1.10.12".
This is causing pipelines using data-diff to break, because of breaking changes with pydantic in version 2.
Would this version be more appropriate:
pydantic = ">=1.10.12, <2.0.0"
The text was updated successfully, but these errors were encountered: