-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Loosen the version constraint of dash-html-components to avoid dependency conflicts #1065
Comments
Dependency tree-----
|
merged with #1062 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, dash locked the version constraint of dash-html-components as dash-html-components ==1.0.2, which leads a troubling scenario to its direct downstream project beeflow which has dependency dash-html-components.
What makes the situation worse is that the downstream projects [skijumpdesign, django-plotly-dash, janggu] of dash are also have dependency dash-html-components.
Could you please loosen the version constraint of dash-html-components?
Benefit of this is that users using both of dash and dash-html-components can upgrade their third party libraries in a timely manner to reduce technical debts.
Solution
The dependency trees of your project and affected downstream projects are shown as follows.
Taking the version constraints of upstream and downstream projects into comprehensive consideration, you can
Loosen click to be dash-html-components >=1.0.2.
Try to add an upper bound for dash-html-components’s version constraint, according to your compatibility.
@chriddyp Please let me know your choice. I can submit a PR to fix this issue.
Thanks for your attention.
Best,
Neolith
The text was updated successfully, but these errors were encountered: