Re: [Numpy-discussion] 1.8.1 release

2014-03-06 Thread Julian Taylor
On 06.03.2014 19:46, Skipper Seabold wrote: > Hi, > > Should [1] be considered a release blocker for 1.8.1? > > Skipper > > [1] https://github.com/numpy/numpy/issues/4442 as far as I can tell its a regression of the 1.8.0 release but not the 1.8.1 release so I wouldn't consider it a blocker. Bu

Re: [Numpy-discussion] 1.8.1 release

2014-03-06 Thread Skipper Seabold
Hi, Should [1] be considered a release blocker for 1.8.1? Skipper [1] https://github.com/numpy/numpy/issues/4442 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] 1.8.1 release

2014-03-02 Thread Oscar Benjamin
On 26 February 2014 22:48, Matthew Brett wrote: > > In that case, the OSX instructions could (within the next few months) > be as simple as: > > Install python from binary installer at python.org > curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py > python get-pip.py > pip install

Re: [Numpy-discussion] 1.8.1 release

2014-02-28 Thread Chris Barker
On Wed, Feb 26, 2014 at 3:10 PM, Tom Augspurger wrote: > Chris Barker - NOAA Federal wrote > > What python are you using? apparently not a Universal 32+64 bit build. > The > > one Apple delivers? > > I'm using homebrew python, so the platform difference seems to have come > from there. and it _s

Re: [Numpy-discussion] 1.8.1 release

2014-02-28 Thread Chris Barker
On Wed, Feb 26, 2014 at 2:48 PM, Matthew Brett wrote: > > Agreed. The trick is that it's reasonable for users of Apple's python > build > > to want this too -- but I don't know how we can hope to provide that. > > We don't support system python for the mpkg, so I think it's > reasonable to leave t

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 3:10 PM, Tom Augspurger wrote: > Thanks Chris, > > > Chris Barker - NOAA Federal wrote >> What python are you using? apparently not a Universal 32+64 bit build. The >> one Apple delivers? > > I'm using homebrew python, so the platform difference seems to have come > fr

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Tom Augspurger
Thanks Chris, Chris Barker - NOAA Federal wrote > What python are you using? apparently not a Universal 32+64 bit build. The > one Apple delivers? I'm using homebrew python, so the platform difference seems to have come from there. I agree about renaming the file as not being a real solution. I'

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 2:33 PM, Chris Barker wrote: > On Wed, Feb 26, 2014 at 11:34 AM, Matthew Brett > wrote: > >> >> > - convention is the other option: >> > - use binary wheel for in-house deplyment to similar systems >> > - use binary wheels for a well-defined python build: >>

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Chris Barker
On Wed, Feb 26, 2014 at 11:34 AM, Matthew Brett wrote: > > - convention is the other option: > > - use binary wheel for in-house deplyment to similar systems > > - use binary wheels for a well-defined python build: > >- for PyPi, that's the python.org builds for Windows and OS-

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 11:02 AM, Chris Barker wrote: > On Wed, Feb 26, 2014 at 8:27 AM, Tom Augspurger > wrote: >> >> Thanks for posting those wheels Matthew. >> >> I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel >> in >> a fresh virtualenv with the latests pip, set

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Frédéric Bastien
Hi, Arnaud finished that in a different way then we had discussed in the PR. https://github.com/numpy/numpy/pull/4081 Fred On Wed, Feb 26, 2014 at 10:07 AM, Frédéric Bastien wrote: > Hi, > > I have a PR that fix way too much printing to stdout when finding the > blas linking information: > > h

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Chris Barker
On Wed, Feb 26, 2014 at 8:27 AM, Tom Augspurger wrote: > Thanks for posting those wheels Matthew. > > I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel in > a fresh virtualenv with the latests pip, setuptools, and wheel. > > ``` > $pip install > ~/Downloads/numpy-1.8.0.dev_a

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Tom Augspurger
Thanks for posting those wheels Matthew. I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel in a fresh virtualenv with the latests pip, setuptools, and wheel. ``` $pip install ~/Downloads/numpy-1.8.0.dev_a89a36e-cp27-none-macosx_10_9_intel.whl numpy-1.8.0.dev_a89a36e-cp27-n

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Frédéric Bastien
Hi, I have a PR that fix way too much printing to stdout when finding the blas linking information: https://github.com/numpy/numpy/pull/4081 This was created by change in NumPy. I was requested as a comment to put the removed information in the dict that we return to the user. I won't have the

Re: [Numpy-discussion] 1.8.1 release

2014-02-25 Thread Carl Kleffner
I build wheels for 32bit and 64bit (Windows, OpenBLAS) and put them here: https://drive.google.com/folderview?id=0B4DmELLTwYmlX05WSWpYVWJfRjg&usp=sharing Due to shortage of time I give not much more detailed informations before 1st of March. Carl 2014-02-25 1:53 GMT+01:00 Chris Barker : > What'

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread RayS
When will we see a http://sourceforge.net/projects/numpy/files/NumPy/1.8.1/Changelog/download changelog? I'd like to get this into our organization's SRS, and a list of fixes (related or not) would be great. - Ray ___ NumPy-Discussion mailing list NumP

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread Chris Barker
What's up with the OpenBLAS work? Any chance that might make it into official binaries? Or is is just too fresh? Also -- from an off-hand comment in the thread is looked like OpenBLAS could provide a library that selects for optimized code at run-time depending on hardware -- this would solve the

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread Matthew Brett
Hi, On Mon, Feb 24, 2014 at 12:40 PM, Matthew Brett wrote: > Hi, > > On Sun, Feb 23, 2014 at 10:26 AM, Charles R Harris > wrote: >> Hi All, >> >> A lot of fixes have gone into the 1.8.x branch and it looks about time to do >> a bugfix release. There are a couple of important bugfixes still to >>

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread Jeff Reback
I am pretty sure that you guys test pandas master but 1.8.1 looks good to me > On Feb 24, 2014, at 4:42 PM, Charles R Harris > wrote: > > > > >> On Mon, Feb 24, 2014 at 1:54 PM, RayS wrote: >> Has anyone alerted C Gohlke? >> http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy >> >> - Ray >

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread Charles R Harris
On Mon, Feb 24, 2014 at 1:54 PM, RayS wrote: > Has anyone alerted C Gohlke? > http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy > > - Ray > Christolph seems to keep a pretty good eye on numpy and we rely on him to test it on windows. In anycase, there are enough fixes backported, that I think we

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread RayS
Has anyone alerted C Gohlke? http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy - Ray ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] 1.8.1 release

2014-02-24 Thread Matthew Brett
Hi, On Sun, Feb 23, 2014 at 10:26 AM, Charles R Harris wrote: > Hi All, > > A lot of fixes have gone into the 1.8.x branch and it looks about time to do > a bugfix release. There are a couple of important bugfixes still to > backport, but if all goes well next weekend, March 1, looks like a good

[Numpy-discussion] 1.8.1 release

2014-02-23 Thread Charles R Harris
Hi All, A lot of fixes have gone into the 1.8.x branch and it looks about time to do a bugfix release. There are a couple of important bugfixes still to backport, but if all goes well next weekend, March 1, looks like a good target date. So give the current 1.8.x branch a try so as to check that i