On Sun, Jun 21, 2015 at 8:13 PM, Charles R Harris <charlesr.har...@gmail.com > wrote:
> > > On Sun, Jun 21, 2015 at 11:49 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> Looks like Scipy 0.13.3 is OK against master apart from a bunch of >> runtime errors due to deprecation warnings, >> > Note that you only get RuntimeWarnings with numpy master, not with a released version (due to switching tests to 'release' mode). > precision changes, >> > That can always happen, those are usually harmless. > TypeErrors due to default casting rule changes, >> > That's the casting='same_kind' I assume? We did that on purpose and thought about it quite hard, so that's OK. If there are other, unintended casting rule changes then I'm not sure. > and new runtime warnings about empty slices. >> > Also not an issue, because they were added on purpose. I think those warnings are a bit too intrusive at the moment, but that's unrelated to Scipy 0.13.3 > I wouldn't recommend it for use with Numpy 1.10, but it is probably not >> fatal to do so. Nothing changes with the deprecation removals added. >> >> > Scipy 0.14.1 is clean except for InvalidValue warnings and is probably the > earliest I'd recommend as "safe". It was released 6 months ago. Scipy > 0.14.0 actually has fewer errors, those resulting from the changes to > default casting rules, so is probably usable also, it was released about a > year ago. > > Ralf, thoughts? > Sounds like we managed to not break anything seriously in numpy master recently, so branching 1.10.x seems OK from this point of view. Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion