From browsing the Suds source code, I get the impression that Suds does not even use the type info specified in the WSDL
files for the results of methods. It just parses whatever XML comes back from the service, converts it to a corresponding
Pythonic data structure, and returns that.
I guess that's ok, except that it means that, to understand what comes back, I have to dig through the WSDL files.
Do any other SOAP clients -- Pythonic or not -- actually use the WSDL-specified method-result types? For what?
For error detection, how useful would it be to have a "result type does not match type declared in WSDL files" exception
thrown at the point where the result comes back, rather than maybe have some random no-such-member exception(s) thrown while
trying to process the result?
How annoying would it be, to have a "result type does not match..." exception thrown, when the mismatch would not have
affected the proper operation of the client code anyway?
I wonder whether I could make Suds just remember the declared type of each method result, and display it in the "print
client" output, purely as human-readable documentation? Maybe just tack another element onto the tuple that represents each
method in the .ports member of the suds.servicedefinition.ServiceDefinition class, and pick it up for display in the
description member function of that class?