On Di, 2014-06-10 at 11:24 +0100, Nathaniel Smith wrote: > On 10 Jun 2014 11:15, "Sebastian Berg" <sebast...@sipsolutions.net> > wrote: > > > > On Di, 2014-06-10 at 10:50 +0100, Nathaniel Smith wrote: > > > On 10 Jun 2014 09:44, "Sebastian Berg" > <sebast...@sipsolutions.net> > > > wrote: > > > > The other error looks a bit different because of the nonzero > logic, > > > but > > > > probably is the same, i.e. also boolean indexing. The last one > is > > > the > > > > change that `arr[[1,2,3,4]] = [1,2]` does not work anymore. A > > > workaround > > > > (maybe also for the rest possibly) is `arr.flat[[1,2,3,4]] = > [1,2]`, > > > but > > > > I guess workarounds are not an option with matplotlib, so have > to > > > think > > > > about it. > > > > > > If the beta is breaking code then let's put the change off to 1.10 > or > > > so and raise a deprecation warning in 1.9. > > > > > > > Yes, unfortunately it is a bit more complicating than that. > > Is it impossible to emulate the old arr[[1, 2, 3, 4]] = [1, 2] > behavior for some reason? Or what do you mean? (I'm not suggesting we > literally go back to the 1.8 indexing code.) >
Yeah, just have to check carefully. Maybe easiest is to just try/except it in C-code, throw a warning, and (if applicable) try calling the `arr.flat[...] = ...` code (which still exists). - Sebastian > -n > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion
signature.asc
Description: This is a digitally signed message part
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
