Was it supposed to be complex128 scalar + float32 array? (And yeah
'casting' is probably a better word than 'upcasting' here.)

On Tue, Feb 5, 2013 at 11:52 AM, Ralf Gommers <notifications@github.com>wrote:

> In doc/release/1.7.0-notes.rst:
>
> > +* the `timedelta64` type (`m`) can now be mixed with any integer type (`b h i l
> > +  q p B H I L Q P`), previously it raised `TypeError`.
> > +
> > +For array + scalar, the above rules just broadcast except the case when
> > +the array and scalars are unsigned/signed integers, then the result gets
> > +converted to the array type (of possibly larger size) as illustrated by the
> > +following examples::
> > +
> > +    >>> (np.zeros((2,), dtype=np.uint8) + np.int16(257)).dtype
> > +    dtype('uint16')
> > +    >>> (np.zeros((2,), dtype=np.int8) + np.uint16(257)).dtype
> > +    dtype('int16')
> > +    >>> (np.zeros((2,), dtype=np.int16) + np.uint32(2**17)).dtype
> > +    dtype('int32')
> > +
> > +Also a ``complex128`` array + ``float32`` array gets upcasted to ``complex64``.
>
> This doesn't parse, complex128 --> complex64 is not upcasting.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/2964/files#r2899148>.
>
>