[SciPy-dev] Duplicate functionality.
Sun Dec 20 19:46:27 CST 2009
On Sun, Dec 20, 2009 at 4:03 PM, Charles R Harris
> Hi All,
> There are two versions of bisection for finding roots, bisect in zeros.py
> and bisection in minpack.py. I think it might be appropriate to deprecate
> bisection with a suggestion to use bisect instead. Along the same lines, I
> think newton should be moved into the zeros module. Thoughts?
First off, are the implementations equivalent, e.g., do they both
return the same results for test cases, and with essentially the same
speed? Are they both implemented at the C level? Both at the Python?
One one way, the other the other? You see where I'm going with this:
make sure you keep the "right" one. :-)
Second, it's been a while, but my recollection is that some
minimization methods (e.g., conjugate gradient) rely fundamentally on
the bisection method, correct? Is bisection called within minpack.py?
More than once? Do you really want to add an import zeros into
minpack.py and replace bisection everywhere with zeros.bisect? (It's
a semi-rhetorical question: I know it's not that big a deal to do so,
"but if it ain't broke, don't fix it"; of course, code divergence is a
source of future breakage...)
Those would be my only concerns about that; as far as moving newton
into zeros, I assume we'd keep a copy where it is through two release
cycles and add a "this has been moved" warning, correct?
More information about the SciPy-Dev