Hi All,
I'm thinking of branching 1.17 this coming (June 15) weekend. The major
components are in: pocketfft, randomgen, and the new sorting routines,
along with default `__array_function__`. They may need a bit of polish, but
I think little remains to be done. If there are other pending PRs that
HI Sebastian,
Thanks for the overview! In the value-based casting, what perhaps surprises
me most is that it is done within a kind; it would seem an improvement to
check whether a given integer scalar is exactly representable in a given
float (your example of 1024 in `float16`). If we switch to
Hi all,
strange, something went wrong sending that email, but in any case...
I tried to "summarize" the current behaviour of promotion and value
based promotion in numpy (correcting a small error in what I wrote
earlier). Since it got a bit long, you can find it here (also copy
pasted at the
signature.asc
Description: This is a digitally signed message part
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
> In a way, I brought it up mostly as a concrete example of an internal
> implementation which we cannot change to an objectively cleaner one because
> other packages rely on an out-of-date numpy API.
>
> Should have added: rely on an out-of-date numpy API where we have multiple
ways for packages
On Tue, 2019-06-11 at 10:56 +0200, Ralf Gommers wrote:
>
>
> On Mon, Jun 10, 2019 at 7:47 PM Marten van Kerkwijk <
> m.h.vankerkw...@gmail.com> wrote:
> > Hi All,
> >
> > In https://github.com/numpy/numpy/pull/12801, Tyler has been trying
> > to use the new `where` argument for reductions to
On Mon, Jun 10, 2019 at 7:47 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Hi All,
>
> In https://github.com/numpy/numpy/pull/12801, Tyler has been trying to
> use the new `where` argument for reductions to implement `nansum`, etc.,
> using simplifications that boil down to
