[Numpy-discussion] Upcoming 1.8 release.
Charles R Harris
Sat Aug 17 13:20:50 CDT 2013
On Sat, Aug 17, 2013 at 11:43 AM, Pauli Virtanen <email@example.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 15.08.2013 19:52, Charles R Harris kirjoitti:
> > On Thu, Aug 15, 2013 at 10:48 AM, Blake Griffith
> > <firstname.lastname@example.org
> >> wrote: I would like to have the ufunc overrides in 1.8 if it is
> >> possible.
> > What is the status of that? I've been leaving that commit up the
> > Pauli.
> I think the PR itself is getting quite complete and does what the spec
> However, I think the fact that the change comes this late in the
> release cycle is sort of a problem. There has not been very much time
> to test it out "in the wild", so we don't know for sure if we'd like
> still to tweak something in the API.
> So I'd either suggest merging the PR labelling this as an experimental
> API in the docs, or if you think this is still too hasty, leave it for
> 1.9. The Numpy C code changes themselves are quite simple and
> localized, so it seems unlikely that they could cause any breakage.
> Getting it in now would have the advantage that we could also manage
> to squeeze in the corresponding user-side part inside scipy.sparse for
> Scipy 0.13.0.
Experimental would be OK if it would help you with Scipy 0.13.0. But if it
does go in and is used in 0.13, won't that effectively lock it in until the
next scipy/numpy release? That seems a bit dangerous if you think some
changes might be warranted. OTOH, the testing might be worth the risk...
My hope is that the next numpy release take much less time than 1.8, which
is almost three releases worth of changes.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion