On Sun, Apr 9, 2017 at 12:14 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:

Le 6 avr. 2017 à 17:21, Ondra Machacek <omachace@redhat.com> a écrit :



On Thu, Apr 6, 2017 at 5:00 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Ho my good, in ovirtsdk.services.py, for every service, there is a different method with a different name that return a associated service, so it's not possible to have a generic like:

def  resolve(service, ...):
id = .....
return service.service(id)

because the generic call service is used by something that take a path argument. But why not a service_by_id(self, id) ?

I am not fully sure I understand what you are missing, but feel free to open
the bug on Python SDK in bugzilla, we will be happy to improve the SDK.

I tried :

I hit a wall. it seems that some of you are not willing to improve the SDK.

That's the beauty of open source.  You can help improving the SDK, instead just complaining. Patches are welcome.

However, I tend to agree with closing the bug - I'd create a library (module) *on top of the SDK* . The comment in the bug is quite clear about it:
"The objective of the SDK is to offer the same that the API offers, without the burden of the details of the HTTP and XML handling. Nothing less, and nothing more."

So improving the SDK where we do not feel it should be improved, may not be the best path. 

Y.