Hey Nathan,
Thanks for taking the time for the detailed answer. I'm still not entirely
convinced by your points. To respond to your points and try and clarify
what I wrote:
> (When you talk about a hierarchy of Exception classes, this is about
making something more convenient than it is
On Mon, Feb 26, 2018 at 11:16 AM, aamit via grpc.io <
grpc-io@googlegroups.com> wrote:
> I had some questions about the api design of RpcError.
>
You're not alone; it's a part of the gRPC Python API that's somewhat
different than how APIs are often shaped in Python (we knew this all along)
and
Hi,
I had some questions about the api design of RpcError. From what I can tell
in docs I should catch RpcError and switch on code (since it's also
implicitly a `Call`). A few things frustrate me about this.
1. There are certain codes I'd like to treat one way and certain codes
I'd like
