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
I recieve the following error on import of the library using:
import dash_leaflet.express as dlx
With the latest version of protobuf also installed (4.21.0 released May 25, 2022)
The error I receive is:
File "...my_page.py", line 10, in <module>
import dash_leaflet.express as dlx
File "/home/.../python3.10/site-packages/dash_leaflet/express.py", line 1, in <module>
import geobuf
File "/home/.../python3.10/site-packages/geobuf/__init__.py", line 1, in <module>
from .encode import Encoder
File "/home/.../python3.10/site-packages/geobuf/encode.py", line 9, in <module>
from . import geobuf_pb2
File "/home/.../python3.10/site-packages/geobuf/geobuf_pb2.py", line 33, in <module>
_descriptor.EnumValueDescriptor(
File "/home/.../python3.10/site-packages/google/protobuf/descriptor.py", line 755, in __new__
_message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot not be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
1. Downgrade the protobuf package to 3.20.x or lower.
2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates
I can confirm the error goes away when downgrading to protobuf 3.20.1
The text was updated successfully, but these errors were encountered:
zach-morris
changed the title
Error with dependancy
Error with dependancy protobuf
May 27, 2022
I recieve the following error on import of the library using:
With the latest version of protobuf also installed (4.21.0 released May 25, 2022)
The error I receive is:
I can confirm the error goes away when downgrading to protobuf 3.20.1
The text was updated successfully, but these errors were encountered: