On Apr 4, 2015 4:12 AM, "Todd" <toddr...@gmail.com> wrote: > > > On Apr 4, 2015 10:54 AM, "Nathaniel Smith" <n...@pobox.com> wrote: > > > > Core python broke backcompat on a regular basis throughout the python > > 2 series, and almost certainly will again -- the bar to doing so is > > *very* high, and they use elaborate mechanisms to ease the way > > (__future__, etc.), but they do it. A few months ago there was even > > some serious consideration given to changing py3 bytestring indexing > > to return bytestrings instead of integers. (Consensus was > > unsurprisingly that this was a bad idea, but there were core devs > > seriously exploring it, and no-one complained about the optics.) > > There was no break as large as this. In fact I would say this is even a larger change than any individual change we saw in the python 2 to 3 switch. The basic mechanics of indexing are just too fundamental and touch on too many things to make this sort of change feasible.
I'm afraid I'm not clever enough to know how large or feasible a change is without even seeing the proposed change. I may well agree with you when I do see it; I just prefer to base important decisions on as much data as possible. -n
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
