[Numpy-discussion] branch 1.17

2019-06-11 Thread Charles R Harris
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

Re: [Numpy-discussion] (Value Based Promotion) Current Behaviour

2019-06-11 Thread Marten van Kerkwijk
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 th

Re: [Numpy-discussion] (Value Based Promotion) Current Behaviour

2019-06-11 Thread Sebastian Berg
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 end)

[Numpy-discussion] (Value Based Promotion) Current Behaviour

2019-06-11 Thread Sebastian Berg
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

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

2019-06-11 Thread Stefan van der Walt
On Tue, 11 Jun 2019 15:10:16 -0400, Marten van Kerkwijk wrote: > 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. This, and the comments Nathaniel m

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

2019-06-11 Thread Marten van Kerkwijk
> 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 t

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

2019-06-11 Thread Marten van Kerkwijk
OK, fair enough to just drop this! In this particular case, I do not care that much about duck-typing, just about making the implementation cleaner (which it is if one doesn't have to worry about diversion via a `.sum()` method). In a way, I brought it up mostly as a concrete example of an intern

[Numpy-discussion] NumPy Community Meeting June 12

2019-06-11 Thread Tyler Reddy
Hi, There will be a NumPy Community meeting on June 12 at 11 am Pacific Time. Anyone is free to join and edit the work-in-progress meeting notes: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?view Best wishes, Tyler ___ NumPy-Discussion mailing list NumPy-Di

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

2019-06-11 Thread Sebastian Berg
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 imp

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

2019-06-11 Thread Ralf Gommers
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 `np.sum(