Dear all,
please find the snapshot
http://pygsl.sf.net/pygsl-snapshot.tar.gz
I finally fixed the memory leak in odeiv.evolve.apply. Correctly the
interface of the "old" function is now found at evolve.apply_vector,
while a simple evolve_apply is now available as well.
This breaks the API, which is not good at all. Does anybody use the
vector method the old API provided (i.e. supplying a vector as t1 and
get the output over the whole vector?). What do you propose? Leave the
old API? I could rename the eval to e.g. eval_single.
I still have problems with some tests of rng. I do not yet understand
where they come from, because when I type the numbers in it works :-(.
Does anybody see problems with rng in everyday usage?
statistics.char uses NPY_BYTE as internal representation.
Sincerely yours
Pierre
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
pygsl-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pygsl-discuss
