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 see this issue was previously closed in #734 but I'm wondering if there are any further plans to switch from google-ai-generativelanguage to the new higher-level python-genai SDK?
My understanding is that the former is for lower-level API access, while the later is more of a facade, as per this comment.
On a personal note, I see the former uses gRPC, while the latter uses REST transport. Although gRPC is faster and switching to REST could arguably be considered a regression, personally I find gRPC is more of a pain for testing purposes, given that most other LLM providers are using REST. Personally I would prefer to be able to use REST for consistency and maintainability in testing (recording event streams with tools like VCRpy etc). I'm not sure if there are plans to support gRPC in the new SDK though, going by this issue googleapis/python-genai#557
The text was updated successfully, but these errors were encountered:
I see this issue was previously closed in #734 but I'm wondering if there are any further plans to switch from google-ai-generativelanguage to the new higher-level python-genai SDK?
My understanding is that the former is for lower-level API access, while the later is more of a facade, as per this comment.
On a personal note, I see the former uses gRPC, while the latter uses REST transport. Although gRPC is faster and switching to REST could arguably be considered a regression, personally I find gRPC is more of a pain for testing purposes, given that most other LLM providers are using REST. Personally I would prefer to be able to use REST for consistency and maintainability in testing (recording event streams with tools like VCRpy etc). I'm not sure if there are plans to support gRPC in the new SDK though, going by this issue googleapis/python-genai#557
The text was updated successfully, but these errors were encountered: