What is more, with the concept of duck-typing, you just have to provide the
interface without inheriting from a mother class (which is what I do for the
optimizer framework, the other sub-modules do not derive from a common
ancestor).
Matthieu
2007/10/17, Renato Serodio <[EMAIL PROTECTED]>:
>
> H
Hello there,
thanks to your pointer, I've progressed further on the OO concept, and
am currently building analysis, inputData and outputResults interfaces
that should add some flexibility to my program.
On the other hand, pulling the OO and interfaces string opened a box
full of little critters,
On Fri, 12 Oct 2007, Renato Serodio apparently wrote:
> The scripts that produce these metrics use Scipy/Numpy
> functions that operate on data conveniently converted to
> numpy arrays. They're quite specific, and I tend to
> produce/tweak a lot of them. So, to fit in this
> application someone
Hello there,
I use NumPy/SciPy to process telemetry, producing some metrics that I
plot with matplotlib. Well, I want to package my scripts into a sort
of all-wrapping application, i.e, the user just calls the app, selects
which metrics to produce and waits to obtain the plots, without being
expos
