-
Notifications
You must be signed in to change notification settings - Fork 220
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
Outdated opentelemetry dependency creating conflicts #2192
Comments
CLOUD-9045 |
FYI:
|
I've also found that MarkupSafe has the same issue, as soda-core 3.4.2 depends on MarkupSafe 2.12 while airflow requires version 2.1.5 |
To add to the discussion, Python 3.7 reached end-of-life in June 2023, a year and a half ago! By the way, Python 3.8 is also end-of-life now. |
Package conflicts when attempting to use soda-core 3.4.3
|
we are blocked on integrating soda into our existing service due to this issue, appreciate if the work can be |
may I ask if there are plans to update telemetry dependencies in the near future? If not, I may have time to look into this following the instructions in CONTRIBUTING.MD. |
Release soda-core version contraint for opentelemetry as there is no reason to support Python 3.7 and this is creating dependency conflicts with many other libraries.
The currently supported versions of opentelemetry are up to 1.22 which are now a year old. This was last changed in march this year via #2043.
The reason I've stumbled across this is due to Airflow no longer supporting opentelemetry <1.22 explicitly in their most recent release.
The package version limit committed to in soda-core in March '24 appears to maintain support for Python 3.7, which makes it more of a tricky discussion I'm sure, however not moving with later versions of other python packages (opentelemetry is just the current problem) will cause many conflicts with other packages in the future I'm sure.
It would be nice to move on from 3.7 which will mean many other packages (e.g markupsafe #2103) can also be bumped.
The text was updated successfully, but these errors were encountered: