-
Notifications
You must be signed in to change notification settings - Fork 16
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
Use correct argument type for valueDecoder method #30
Conversation
@silent-nekto, @dmiller7, @haxtibal, could you please check that this change fixes #28 issue for you? |
Changing the lambda for the recursiveFlag=True case seems correct, afaikt. Sadly it's not sufficient to resolve the pysnmp error. pysnmp passes its own lambdas as substrateFun into the decoder. We can't change that from pyasn1 code base. Changing the substrateFun signature was an API breakage, so I'm afraid clients (like pysnmp) need to be adapted. In 93e11a2, Ilya mentioned
But that doesn't seem to keep substrateFun compatible, does it? |
@droideck sorry this didn't work for me - as @haxtibal has said the pysnmp error is still present for me. I'm guessing that a short term fix might be for pysnmp to change its dependencies from
to
But I don't think I know enough to be sure. I was hoping that a fix might be put in place here rather than pysnmp as I think pysnmp seems to be between maintainers. |
https://pypi.org/project/pysnmplib/ has picked up pysnmp edit: this turned out to be a unresolvable dependency hell conflict between It would be nice to let them know about the breaking change as everything is failing with
|
@bdraco what you said is completely wrong. |
You are right about that (although not the nicest way to say it). It looks like there we have a dep conflict somewhere since we are getting both installed and |
Its actually much worse dep hell since both
|
Opened pysnmp/pysnmp#51 to see if |
@bdraco This is not a dep hell, but what naturally happened when people tried to save a collapsed stack like |
No description provided.