[Numpy-discussion] tests for casting table? (was: Numpy 1.7b1 API change cause big trouble)

Nathaniel Smith njs@pobox....
Thu Sep 20 15:09:16 CDT 2012


On Mon, Sep 17, 2012 at 10:22 AM, Matthew Brett <matthew.brett@gmail.com> wrote:
> Hi,
>
> On Sun, Sep 9, 2012 at 6:12 PM, Frédéric Bastien <nouiz@nouiz.org> wrote:
>> The third is releated to change to the casting rules in numpy. Before
>> a scalar complex128 * vector float32 gived a vector of dtype
>> complex128. Now it give a vector of complex64. The reason is that now
>> the scalar of different category only change the category, not the
>> precision. I would consider a must that we warn clearly about this
>> interface change. Most people won't see it, but people that optimize
>> there code heavily could depend on such thing.
>
> It seems to me that it would be a very good idea to put the casting
> table results into the tests to make sure we are keeping track of this
> kind of thing.
>
> I'm happy to try to do it if no-one else more qualified has time.

I haven't seen any PRs show up from anyone else in the last few days,
and this would indeed be an excellent test to have, so that would be
awesome.

-n


More information about the NumPy-Discussion mailing list