-
Notifications
You must be signed in to change notification settings - Fork 12
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
protobuf 3.2.0 not working but protobuf 3.1.0.post1 is #30
Comments
Note: I was able to get around this by pinning |
This was written long before protobuf 3, so unfortunately I don't know what would cause this specific error. I'll look into it if I get a chance, but for the time being I'll gladly accept a PR to depend on |
Thanks, I'll go ahead and make the PR. I'll also see if I can find some other verification of the root cause of the issue and whether it's needed for Python 3 also as we're running 2.7. |
More information on the problem here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835271 . We didn't experience this problem until we upgraded Debian. It's not at all a pull request, but I was able to "fix" this issue for myself by trivially replacing riemann_pb2.py with the python 3 implementation (since I'm using python 3, I don't care about the python 2 implementation). |
I might not be reading the bug correctly, but it sounds like renaming |
Reading the underlying change in the protobuf library, I believe this will work. |
Getting the following stack trace error when trying to start up an application that's using riemann-client:
This is happening with protobuf 3.2.0 only. When I manually move the protobuf 3.1.0.post1 site-package from my last build into my app env everything works as expected.
I notice that the wheels are built differently and vary greatly in size as well:
vs
Does the riemann-client need to be forced to use protobuf < 3.2 or is there a problem outside the scope of riemann-client that I'm not recognizing?
The text was updated successfully, but these errors were encountered: