You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
Hi, as shown in the following full dependency graph of historical, historical requires marshmallow (the latest version), while the installed version of swag-client(0.4.3) requires marshmallow>=2.13.5,<3.0.0.
According to Pip's “first found wins” installation strategy, marshmallow 2.19.5 is the actually installed version.
Although the first found package version marshmallow 2.19.5 just satisfies the later dependency constraint (marshmallow>=2.13.5,<3.0.0), it will lead to a build failure once developers release a newer version of marshmallow.
Fix your direct dependencies to be marshmallow>=2.13.5,<3.0.0 to remove this conflict.
I have checked this revision will not affect your downstream projects now.
Build a good dependency ecosystem for python projects is our common goal. ^_^
@mikegrima May I pull a request to solve this issue?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, as shown in the following full dependency graph of historical, historical requires marshmallow (the latest version), while the installed version of swag-client(0.4.3) requires marshmallow>=2.13.5,<3.0.0.
According to Pip's “first found wins” installation strategy, marshmallow 2.19.5 is the actually installed version.
Although the first found package version marshmallow 2.19.5 just satisfies the later dependency constraint (marshmallow>=2.13.5,<3.0.0), it will lead to a build failure once developers release a newer version of marshmallow.
Dependency tree--------
Thanks for your attention.
Best,
Neolith
The text was updated successfully, but these errors were encountered: