Re: [Numpy-discussion] Numpy 1.11.0b2 released

2016-01-31 Thread Marten van Kerkwijk
Hi Julian, While the numpy 1.10 situation was bad, I do want to clarify that the problems we had in astropy were a consequence of *good* changes in `recarray`, which solved many problems, but also broke the work-arounds that had been created in `astropy.io.fits` quite a long time ago (possibly bef

Re: [Numpy-discussion] Numpy pull requests getting out of hand.

2016-01-31 Thread Jeff Reback
FYI also useful to simply close by time - say older than 6 months with a message for the writer to reopen if they want to work on it then u don't get too many stale ones my 2c > On Jan 31, 2016, at 2:10 PM, Charles R Harris > wrote: > > Hi All, > > There are now 130 open numpy pull request

[Numpy-discussion] Numpy pull requests getting out of hand.

2016-01-31 Thread Charles R Harris
Hi All, There are now 130 open numpy pull requests and it seems almost impossible to keep that number down. My personal decision is that I am going to ignore any new enhancements for the next couple of months and only merge bug fixes, tests, house keeping (style, docs, deprecations), and old PRs.

Re: [Numpy-discussion] Downstream integration testing

2016-01-31 Thread Pauli Virtanen
31.01.2016, 14:41, Daπid kirjoitti: > On 31 Jan 2016 13:08, "Pauli Virtanen" wrote: >> For example, automated test rig that does the following: >> >> - run tests of a given downstream project version, against >> previous numpy version, record output >> >> - run tests of a given downstream projec

Re: [Numpy-discussion] Downstream integration testing

2016-01-31 Thread Daπid
On 31 Jan 2016 13:08, "Pauli Virtanen" wrote: > For example, automated test rig that does the following: > > - run tests of a given downstream project version, against > previous numpy version, record output > > - run tests of a given downstream project version, against > numpy master, record

[Numpy-discussion] Downstream integration testing

2016-01-31 Thread Pauli Virtanen
31.01.2016, 12:57, Julian Taylor kirjoitti: [clip] > Testing or delegating testing of least our major downstreams should be > the job of the release manager. > Thus I also disagree with our more frequent releases. It puts too much > porting and testing effort on our downstreams and it gets infeaseb

Re: [Numpy-discussion] Numpy 1.11.0b2 released

2016-01-31 Thread Julian Taylor
On 01/30/2016 06:27 PM, Ralf Gommers wrote: > > > On Fri, Jan 29, 2016 at 11:39 PM, Nathaniel Smith > wrote: > > It occurs to me that the best solution might be to put together a > .travis.yml for the release branches that does: "for pkg in > IMPORTANT_PACKAGE

Re: [Numpy-discussion] Numpy 1.11.0b1 is out

2016-01-31 Thread Sebastian Berg
On Sa, 2016-01-30 at 20:27 +0100, Derek Homeier wrote: > On 27 Jan 2016, at 1:10 pm, Sebastian Berg < > sebast...@sipsolutions.net> wrote: > > > > On Mi, 2016-01-27 at 11:19 +, Nadav Horesh wrote: > > > Why the dot function/method is slower than @ on python 3.5.1? > > > Tested > > > from the l