Skip to content
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

Relax protobuf dependencies further in python package #390

Open
holtgrewe opened this issue Sep 7, 2024 · 4 comments · May be fixed by #393
Open

Relax protobuf dependencies further in python package #390

holtgrewe opened this issue Sep 7, 2024 · 4 comments · May be fixed by #393
Assignees

Comments

@holtgrewe
Copy link

You are limiting the protobuf versions to >=3.20.2,<4.0.0. Is this necessary? protobuf 4.x is available since 2022.

"protobuf>=3.20.2,<4.0.0",

This prevents anything else depending on phenopackets to use a more recent protobuf version.

@julesjacobsen
Copy link
Collaborator

@iimpulse can you look into this, please?

@gilmorera
Copy link

@iimpulse This is also an issue for me. Is there a specific reason the version is pinned?

@ielis
Copy link
Contributor

ielis commented Jan 13, 2025

Hi @gilmorera @holtgrewe

Is there a specific reason the version is pinned?

Phenopacket Schema uses Protobuf 3.20.3:

<protobuf.version>3.20.3</protobuf.version>

therefore, out of caution, we allow protobuf<4.0.0, per Semantic versioning. In principle, protobuf>=4.0.0 may work OK, it's hard to be sure though..


I would like to fix this issue with a PR where that checks if the messages serialized by protobuf-java==3.20.3 are decoded properly with a newer Python protobuf.

This seems to work for Python bindings generated with Protobuf compiler 3.20.3 (in Phenopacket Schema) or with 4.29.3 (latest protobuf-java) and for protobuf==5.29.3 (latest Protobuf release for Python).

I'll be posting updates here..

@ielis ielis linked a pull request Jan 13, 2025 that will close this issue
@gilmorera
Copy link

Thanks for your quick response. I'll check back later for your updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants