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 was archived by the owner on Aug 13, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 13, 2026. It is now read-only.
python3-protobuf is not compatible with protobuf #526
protobuf is one of the dependencies for google-cloud-bigquery
Once I do pip install google-cloud-bigquery it install protobuf. Then riak library stops working.
I always get the error like this:
File "/usr/local/lib/python3.5/dist-packages/google/protobuf/descriptor.py", line 824, in new
return _message.default_pool.AddSerializedFile(serialized_pb)
TypeError: expected bytes, str found
The possible solution: seems like protobuf version 3.4 works fine with python 3. So maybe it would be better to use protobuf instead of python3-protobuf
We had to vendorize the riak-python-client into our project and fix it. However, we'll looking for alternatives to RiakKV since it's really dead. We only fixed it for our project (https://github.com/merchise/kaircs).
@acehko Same here. Can you share your candidates list with us? So far, we have considered and discarded Voldemort. We have even implemented a proof-of-concept CRDTs in Python (https://github.com/merchise/xotl.crdt); because our distribution requirements are not the "usual" ones (we don't require more than one server in each datacenter, but we do require fast (nearest) access Europe and America).
Activity
mvaled commentedon Dec 12, 2017
Would this be the responsible of:
Reorganize the package to provide our vendorized riak client.
acehko commentedon Nov 7, 2018
I have a similar issue.
Did anyone find a workaround for this?
mvaled commentedon Nov 8, 2018
@acehko
We had to vendorize the riak-python-client into our project and fix it. However, we'll looking for alternatives to RiakKV since it's really dead. We only fixed it for our project (https://github.com/merchise/kaircs).
acehko commentedon Nov 8, 2018
@mvaled
Thanks. We're also looking for an alternative, but it will be a while before we can completely migrate.
mvaled commentedon Nov 8, 2018
@acehko Same here. Can you share your candidates list with us? So far, we have considered and discarded Voldemort. We have even implemented a proof-of-concept CRDTs in Python (https://github.com/merchise/xotl.crdt); because our distribution requirements are not the "usual" ones (we don't require more than one server in each datacenter, but we do require fast (nearest) access Europe and America).