So, raise a ValueError when it used to return (mostly) correct results? For some reason, I don't think people would appreciate that.
Ben Root On Jan 13, 2015 5:59 PM, "Chris Barker" <[email protected]> wrote: > On Tue, Jan 13, 2015 at 7:23 AM, Benjamin Root <[email protected]> wrote: > >> Oh, wow. I never noticed that before. Yeah, if I state that retstep=True, >> then I am coding my handling to expect two values to be returned, not 1. I >> think it should be nan, but I could also agree with zero. It should >> definitely remain a float value, though. >> > > How about a ValueError? > > -CHB > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > [email protected] > > _______________________________________________ > NumPy-Discussion mailing list > [email protected] > http://mail.scipy.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
