Another approach, maybe more suited for your use case, would be to not use the client object and interract directly with the service level and the connection (since you seem to want to process the data outside of python).

This example should be useful to you.

Since you want to craft a request but not interpret the resposne (which the client does), you could do something like :

In the above example, didconfig is the same config used by the client. The didconfig is not necessary to craft the request, it is just validated to fail early instead of sending a request and waiting for a response to then fail. I should have made that parameter optional.. you can put any valid configuration that won't affect the request.

You could even be more clever and use the client send_request method. All client method does the same thing. It calls : service.make_request, client.send_request, service.interpret_response + do some sanity checks. Meaning, something like that would work.

You may have notice the usage of the exception. I wanted to show it to you because you use none in your above code. :) The client raises exception. You can disable them with the configuration, bu you still need to check yourself if the response is valid/negative/unexpected. The response will only be None if you use SuppressPositiveResponse.

TimeoutException cannot be disabled in the client.

Ok, that's enough. Have fun