Re: [grpc-io] Safe to modify message object after yielded to a request/response stream? (Python)

2018-03-29 Thread james . oldfield . london
Thanks a lot for responding Nathaniel. In honesty the use case is very slight simplification to a utility generator function. The difference is only a couple of lines, and arguably it would be clearer to explicitly create a new request each time anyway. As you don't guarantee this behaviour,

[grpc-io] Re: Safe to modify message object after yielded to a request/response stream? (Python)

2018-03-29 Thread james . oldfield . london
Follow up: Would the answer be any different if I was using the non-blocking API: request_iter = my_iter(RequestType(), data) response_future = my_stub.streaming_request.future(request_iter) -- You received this message because you are subscribed to the Google Groups "grpc.io" group.

[grpc-io] Safe to modify message object after yielded to a request/response stream? (Python)

2018-03-29 Thread james . oldfield . london
Consider the following snippet: def my_iter(some_request, extra_data_list): for item in extra_data_list: some_request.extra = item yield some_request some_request.Clear() # ... some time later ... response =