Re: [Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

Hi Chuck, others, A propos __numpy_ufunc__, what is the current status? Is it still the undetermined result of the monster-thread ( https://github.com/numpy/numpy/issues/5844 -- just found it again by sorting by number of comments...)? As noted by Stephan and myself when the decision was made to

Re: [Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

I'll echo Marten's sentiments. I've found __numpy_ufunc__ as it exists in the master branch to be quite useful in my experiments with sparse arrays ( https://github.com/perimosocordiae/sparray), and I think it'll be a net benefit to scipy.sparse as well (despite the unpleasantness with __mul__).

Re: [Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

On Tue, Jan 5, 2016 at 6:17 PM, CJ Carey wrote: > I'll echo Marten's sentiments. I've found __numpy_ufunc__ as it exists in > the master branch to be quite useful in my experiments with sparse arrays ( > https://github.com/perimosocordiae/sparray), and I think it'll be

Re: [Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

On Tue, Jan 5, 2016 at 4:55 PM, Marten van Kerkwijk wrote: > Hi Chuck, others, > > A propos __numpy_ufunc__, what is the current status? Is it still the > undetermined result of the monster-thread > (https://github.com/numpy/numpy/issues/5844 -- just found it again by >

[Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

Hi All, I'm going to attempt a 1.10.3 release tomorrow to address the segfault reported in #6922 . I'd also like to branch 1.11.x sometime this month, hopefully around Jan 18 (two weeks from now). There are some unresolved issues, in particular