pcp
[Top] [All Lists]

Re: fetchgroups api - python bindings

To: myllynen@xxxxxxxxxx
Subject: Re: fetchgroups api - python bindings
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Tue, 08 Dec 2015 09:16:52 -0500
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5666E4F7.4070005@xxxxxxxxxx> (Marko Myllynen's message of "Tue, 8 Dec 2015 16:11:03 +0200")
References: <20151206204742.GC22561@xxxxxxxxxx> <5666E4F7.4070005@xxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Hi, Marko -

Thanks for the reviews!

>> v = pmfg.extend_item("hinv.ncpu", c_api.PM_TYPE_U32)
>> vv = pmfg.extend_indom("kernel.all.load", c_api.PM_TYPE_FLOAT)
>
> - I mentioned about this earlier relating to the C API but I think it's
> worth checking again with the Python side: has the type argument really
> be mandatory here? If the user don't pass it, it'd require two lines to
> figure it out in the Python layer on the user's behalf and the user can
> later on do type(v()) or str(v()) or such as needed. [...]

You've got a pretty good case with python, since it's so dynamically
typed already.  OK, will accept None.


> - Regardless of the above, perhaps it might be better to define
> extend_item(self, metric=None, mtype=None, scale=None, instance=None)
> instead of
> extend_item(self, metric=None, mtype=None, instance=None, scale=None)

You're right.


- FChE

<Prev in Thread] Current Thread [Next in Thread>