-
Notifications
You must be signed in to change notification settings - Fork 237
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 junos-eznc version #457
Comments
Suggested Solution
@dbarrosop Which solution do you prefer, 1 or 2? |
I think we should do 2 i.e. remove the direct dependency on The other option is to pin the direct dependency to 2.2.1. The cause was a change that PyEZ library made that broke napalm tests--it is only a testing issue and not a real issue (i.e. we mocked a PyEZ connection and are now missing a needed attribute in napalm). The issue will be fixed in the next NAPALM release. Though we will have to roll Nornir pyproject.toml for that anyways as it will be NAPALM 3.X.X. |
if we don't directly use |
Thanks a lot for reporting the issue and for the extensive analysis and proposed solutions. I concur with Kirk and Dimitri, I think removing the direct dependency is the best solution. |
@dbarrosop @dmfigol @ktbyers, Thanks for your quick feedback. I will submit a PR to solve this problem. :-P |
Remove junos-eznc dependency, fix nornir-automation#457
Remove junos-eznc dependency, fix nornir-automation#457
Remove junos-eznc dependency, fix #457
Hi, users are unable to run nornir due to dependency conflict with junos-eznc package. As shown in the following full dependency graph of nornir, napalm requires junos-eznc ==2.2.1,while nornir requires junos-eznc >=2.2,<3.0.
According to pip’s “first found wins” installation strategy, junos-eznc 2.3.1 is the actually installed version. However, junos-eznc 2.3.1 does not satisfy ==2.2.1.
Dependency tree-----------
Thanks for your help.
Best,
Neolith
The text was updated successfully, but these errors were encountered: