Skip to content

Allow grpcio >=1.63.0#862

Open
springmeyer wants to merge 3 commits into
triton-inference-server:mainfrom
springmeyer:springmeyer/allow-recent-grpcio
Open

Allow grpcio >=1.63.0#862
springmeyer wants to merge 3 commits into
triton-inference-server:mainfrom
springmeyer:springmeyer/allow-recent-grpcio

Conversation

@springmeyer

@springmeyer springmeyer commented Nov 11, 2025

Copy link
Copy Markdown

grpcio is now at 1.76.0 (https://pypi.org/project/grpcio/). grpcio>1.75.1 supports binary wheels for python 3.14 (grpc/grpc#40403), which would be useful to leverage in this project.

@Kuraiou

Kuraiou commented Feb 26, 2026

Copy link
Copy Markdown

Is there any chance that this can be prioritized for review, approval, and merge?

@springmeyer

Copy link
Copy Markdown
Author

I noticed @whoisj just addressed a similar issue with protobuf in 39dcd33.

@whoisj could you integrate this one as well?

@whoisj

whoisj commented Feb 26, 2026

Copy link
Copy Markdown
Contributor

@springmeyer, I don't see your name in our list of people who've completed the required CLA paperwork. Could you be sure to complete this? Thank you.

@springmeyer

Copy link
Copy Markdown
Author

@whoisj good to know. I'm happy to sign the CLA, but perhaps it would be easier for you to just commit this directly (as I don't have further changes to provide at this point)?

@Miskho

Miskho commented Apr 22, 2026

Copy link
Copy Markdown

@springmeyer @whoisj Is there any way this can be revisited in time of the next release?

grpc 1.80 is already more then 1 and half years old (Nov 2024).

Is there any suggested way how to go around this limitation or should we just fork and rebuild locally?

@whoisj

whoisj commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

@Miskho it is on my TODO list, but the ship for our 26.04 release has already sailed. We generally create releases at the start of a month, spend the month with QA validating them, then release them at the end of the month. Earliest I could get this change in for would be 26.05; hopefully that meets your needs.

@reinoldus

Copy link
Copy Markdown

@whoisj thank you for looking into it. Can you already provide an update on this matter?

@soenmezanil

Copy link
Copy Markdown

@whoisj would be great to hear an update on this!

@whoisj

whoisj commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@zanilzanzan, this has been an ongoing background task of mine. Turns out there are a lot of places that need to be updated to make this succeed. I'll keep working through the issues and hopefully get this done in time for our 26.07 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

6 participants