[Numpy-discussion] 1.10.0rc1

[Charles R Harris]

On Wed, Aug 26, 2015 at 7:11 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Tue, 25 Aug 2015 10:26:02 -0600
> Charles R Harris <charlesr.harris at gmail.com> wrote:
> > Hi All,
> >
> > The silence after the 1.10 beta has been eerie. Consequently, I'm
> thinking
> > of making a first release candidate this weekend. If you haven't yet
> tested
> > the beta, please do so. It would be good to discover as many problems as
> we
> > can before the first release.
>
> Has typing of ufunc parameters become much stricter? I can't find
> anything in the release notes, but see (1.10b1):
>
> >>> arr = np.linspace(0, 5, 10)
> >>> out = np.empty_like(arr, dtype=np.intp)
> >>> np.round(arr, out=out)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File
> "/home/antoine/np110/lib/python3.4/site-packages/numpy/core/fromnumeric.py",
> line 2778, in round_
>     return round(decimals, out)
> TypeError: ufunc 'rint' output (typecode 'd') could not be coerced to
> provided output parameter (typecode 'l') according to the casting rule
> ''same_kind''
>
>
> It used to work (1.9):
>
> >>> arr = np.linspace(0, 5, 10)
> >>> out = np.empty_like(arr, dtype=np.intp)
> >>> np.round(arr, out=out)
> array([0, 1, 1, 2, 2, 3, 3, 4, 4, 5])
> >>> out
> array([0, 1, 1, 2, 2, 3, 3, 4, 4, 5])
>

The default casting mode has been changed. I think this has been raising a
warning since 1.7 and was mentioned as a future change in 1.10, but you are
right, it needs to be mentioned in the 1.10  release notes.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20150826/474e588b/attachment.html>