[Numpy-discussion] broadcasting behavior for 1.6 (was: Numpy 1.6 schedule)

Benjamin Root ben.root@ou....
Fri Mar 11 16:42:51 CST 2011


On Fri, Mar 11, 2011 at 4:33 PM, Charles R Harris <charlesr.harris@gmail.com
> wrote:

>
>
> On Fri, Mar 11, 2011 at 1:10 PM, Mark Wiebe <mwwiebe@gmail.com> wrote:
>
>> On Fri, Mar 11, 2011 at 8:19 AM, Travis Oliphant <oliphant@enthought.com>wrote:
>>
>>> This discussion is interesting and useful for NumPy 2.0, but the subtle
>>> change is not acceptable for NumPy 1.6.
>>>
>>> The rules were consistent, even if seen as unintuitive by some.
>>>
>>> The fact that two libraries we know of already had tests break should be
>>> a big red warning flag.  There are a lot of other libraries that may have
>>> tests break.
>>>
>>> Having to fix tests would be expected for NumPy 2.0, but not 1.6.
>>>
>>> I am a big -10 for rolling out a change like this in NumPy 1.6
>>>
>>
>> I've pushed a patch to change this, with tests.
>>
>>
> I'm impressed by how little you needed to change.
>
> <snip>
>
> Chuck
>
>
Should tests be added to detect future changes?

Ben Root
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20110311/ce16618a/attachment-0001.html 


More information about the NumPy-Discussion mailing list