
On Tue, Jan 13, 2015 at 6:02 PM, Benjamin Root <ben.root@ou.edu> wrote:
So, raise a ValueError when it used to return (mostly) correct results?
my understanding is that it was NOT returning mostly correct results, it was returning completely different results for those special values: a 2-tuple in most cases, a single array if there delta didn't make sense. That may be correct, but it's not a result ;-) That being said, I'm sure some folks have written work-arounds that would break if this were changed. A bug is always incorporated in someones workflow. http://xkcd.com/1172/ Though if you do have a work-around for when the step is not returned, it will likely break if suddenly zero or NaN is returned, as well. So I'm not sure there is a fully backward compatible fix. -CHB
For some reason, I don't think people would appreciate that.
Ben Root On Jan 13, 2015 5:59 PM, "Chris Barker" <chris.barker@noaa.gov> wrote:
On Tue, Jan 13, 2015 at 7:23 AM, Benjamin Root <ben.root@ou.edu> 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
Chris.Barker@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- 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 Chris.Barker@noaa.gov