[SciPy-dev] Scipy workflow (and not tools).

Brian Granger ellisonbg.net@gmail....
Thu Feb 26 11:39:22 CST 2009


> As another long time lurker I would also support everything Neil said.
>
> I also wanted to add the point, that what stops me recommending scipy
> more widely to my colleagues is not that there is not enough code in
> it - it is that it is not stable enough to rely on for their work.
> That is perhaps a bit harsh, but I am sure that the first time one of
> my colleagues lost 1/2 a day because of a scipy bug (as I have done
> quite a few times) they would be back to MATLAB.
>
> So I would agree with Stefan and the others that the priority is not
> getting more code in per se, but improving the quality and frequency
> of releases to get a platform whose stability compares with MATLAB
> before adding more stuff.

+1


More information about the Scipy-dev mailing list