-
Notifications
You must be signed in to change notification settings - Fork 0
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
Installation fails due to conflicting pyyaml version #39
Comments
Suggested Solution
@garyd203 Which solution do you prefer, 1, 2 or 3? |
Hi @NeolithEra , thanks a lot for the detailed bug report. This issue hadn't affected me because I have been using For a solution, it's not desirable to loosen the The best approach seems to be if we restrict our version of |
I will pick this up |
As described in #39 the version resolution for `pip` will pick up the more lenient version range for `ssmash` before it finds the restrictive version range for `flying-circus`. The bets compromise seems to be to pin our version to that of `flying-cirucs`.
As described in #39 the version resolution for `pip` will pick up the more lenient version range for `ssmash` before it finds the restrictive version range for `flying-circus`. The bets compromise seems to be to pin our version to that of `flying-cirucs`.
As described in #39 the version resolution for `pip` will pick up the more lenient version range for `ssmash` before it finds the restrictive version range for `flying-circus`. The bets compromise seems to be to pin our version to that of `flying-cirucs`.
Appears to be resolved now. Thanks @NeolithEra :)
|
Hi, users are unable to run ssmash due to dependency conflict with pyyaml package. As shown in the following full dependency graph of ssmash, ssmash requires pyyaml >=5.1,<6,while flying-circus requires <5.2.0,>=5.1.1.
According to pip’s “first found wins” installation strategy, pyyaml 5.2 is the actually installed version. However, pyyaml 5.2 does not satisfy PyYAML<5.2.0,>=5.1.1.
Dependency tree-----------
Thanks for your help.
Best,
Neolith
The text was updated successfully, but these errors were encountered: