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
The python samples don't run on Ubuntu 24 anymore, as the default protobuf version is newer and thus not backwards compatible anymore to the current sample files, e.g. person.proto.
As a workaround, the user himself can generate the files again with a current protobuf compiler in the samples folder.
However, for creating releases it would be nice to generator those file during the build process.
How to reproduce
--
How did you get eCAL?
Custom Build / Built from source
Environment
--
eCAL System Information
--
The text was updated successfully, but these errors were encountered:
Peguen
changed the title
[Python] Generate protofiles for python samples during build
[Python] Python samples do not work on Ubuntu 24 anymore out of the box due to protobuf incompatibility
Oct 18, 2024
After compiling with the newer protobuf version, Unable to link eCAL and eclipse kuksa due to incompatibility.
TypeError: Descriptors cannot 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)
How to reproduce?
Compile the proto file from the ecal2val and run ecal2val.py
Thanks for reporting. I think the Python Protobuf API changed after version 3.21, this is why we have a version requirement in our requirements.txt file.
We'll have to rework / check our python implementation for newer protobuf versions.
Problem Description
The python samples don't run on Ubuntu 24 anymore, as the default protobuf version is newer and thus not backwards compatible anymore to the current sample files, e.g. person.proto.
As a workaround, the user himself can generate the files again with a current protobuf compiler in the samples folder.
However, for creating releases it would be nice to generator those file during the build process.
How to reproduce
--
How did you get eCAL?
Custom Build / Built from source
Environment
--
eCAL System Information
The text was updated successfully, but these errors were encountered: