gRPC-python wraps gRPC-Core as they are in the same repo. So if you go to
the specific git tag,
e.g. https://github.com/grpc/grpc/tree/v1.58.0/third_party, you can find
the commit of the BorgingSSL dependency (boringssl-with-bazel ...). In this
case of 1.58.0,
it's
And what is the BoringSSL version used there? How do we decipher it
On Wednesday, September 13, 2023 at 11:21:59 PM UTC+5:30 AJ Heller wrote:
> I'm not entirely sure how to help you with such an old version. I'd
> recommend trying with a more recent gRPC version, we are currently up to
>
I'm not entirely sure how to help you with such an old version. I'd
recommend trying with a more recent gRPC version, we are currently up to
version 1.58. https://pypi.org/project/grpcio/
On Monday, September 11, 2023 at 3:40:12 AM UTC-7 Reena THOMAS wrote:
> I am downloading tar file from
>
