Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 6:07 PM, Nathaniel Smith wrote: > On Mon, Feb 8, 2016 at 6:04 PM, Matthew Brett wrote: >> On Mon, Feb 8, 2016 at 5:26 PM, Nathaniel Smith wrote: >>> On Mon, Feb 8, 2016 at 4:37 PM, Matthew Brett >>> wrote: >>> [...] I can't replicate the segfault with manylinux whee

Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 6:04 PM, Matthew Brett wrote: > On Mon, Feb 8, 2016 at 5:26 PM, Nathaniel Smith wrote: >> On Mon, Feb 8, 2016 at 4:37 PM, Matthew Brett >> wrote: >> [...] >>> I can't replicate the segfault with manylinux wheels and scipy. On >>> the other hand, I get a new test error fo

Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 5:26 PM, Nathaniel Smith wrote: > On Mon, Feb 8, 2016 at 4:37 PM, Matthew Brett wrote: > [...] >> I can't replicate the segfault with manylinux wheels and scipy. On >> the other hand, I get a new test error for numpy from manylinux, scipy >> from manylinux, like this: >> >

Re: [Numpy-discussion] GSoC?

Is there a clean way of importing existing C code as a vectorized numpy func? Like, it would be awesome to use gdal in a vectorized way just with ctypes or something. Just something I've dreamed of that I thought I'd ask about in regards to the GSoC. Elliot On Feb 8, 2016 6:03 PM, "Chris Barker"

Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 4:37 PM, Matthew Brett wrote: [...] > I can't replicate the segfault with manylinux wheels and scipy. On > the other hand, I get a new test error for numpy from manylinux, scipy > from manylinux, like this: > > $ python -c 'import scipy.linalg; scipy.linalg.test()' > >

Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 10:23 AM, Matthew Brett wrote: > On Mon, Feb 8, 2016 at 3:57 AM, Evgeni Burovski > wrote: >> -- Forwarded message -- >> From: Evgeni Burovski >> Date: Mon, Feb 8, 2016 at 11:56 AM >> Subject: Re: [Numpy-discussion] Multi-distribution Linux wheels - please t

Re: [Numpy-discussion] GSoC?

As you can see in the timeline: https://developers.google.com/open-source/gsoc/timeline We are now in the stage where mentoring organizations are getting their act together. So the question now is -- are there folks that want to mentor for numpy projects? It can be rewarding, but it's a pretty bi

Re: [Numpy-discussion] GSoC?

sir actually i am interested very much . so can you help me about this or suggest some , so that i can contribute . Thanks & Regards, Smruti Ranjan Sahoo On Tue, Feb 9, 2016 at 1:58 AM, Chris Barker wrote: > ANyone interested in Google Summer of Code this year? > > I think the real challe

Re: [Numpy-discussion] Linking other libm-Implementation

> Am 08.02.2016 um 18:36 schrieb Nathaniel Smith : > > On Feb 8, 2016 3:04 AM, "Nils Becker" > wrote: > > > [...] > > Very superficial benchmarks (see below) seem devastating for gnu libm. It > > seems that openlibm (compiled with gcc -mtune=native -O3) performs r

[Numpy-discussion] GSoC?

ANyone interested in Google Summer of Code this year? I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it -- numpy could really benefit. Maybe as a python.org sub-project? https://wiki.python.org/moin/SummerOfCode/2016 Deadlines are

Re: [Numpy-discussion] Numpy 1.11.0b2 released

On Sat, Feb 6, 2016 at 4:11 PM, Michael Sarahan wrote: > Chris, > > Both conda-build-all and obvious-ci are excellent projects, and we'll > leverage them where we can (particularly conda-build-all). Obvious CI and > conda-smithy are in a slightly different space, as we want to use our own > anac

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

Hi Julian, On Mon, Feb 8, 2016 at 8:40 AM, Julian Taylor wrote: > On 02/08/2016 05:23 PM, Daπid wrote: >> >> On 8 February 2016 at 16:19, Olivier Grisel > > wrote: >> >> >> >> OPENBLAS_CORETYPE=Nehalem python3 -c "import numpy as np; from scipy >> import l

Re: [Numpy-discussion] [SciPy-Dev] Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 10:41 AM, Evgeni Burovski wrote: > >> numpy.show_config() shows the places that numpy found the libraries at >> build time. In the case of the manylinux wheel builds, I put openblas >> at /usr/local , but the place the wheel should be loading openblas >> from is /.libs. Fo

Re: [Numpy-discussion] [SciPy-Dev] Multi-distribution Linux wheels - please test

> numpy.show_config() shows the places that numpy found the libraries at > build time. In the case of the manylinux wheel builds, I put openblas > at /usr/local , but the place the wheel should be loading openblas > from is /.libs. For example, I think you'll > find that the numpy tests will stil

Re: [Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

On Mon, Feb 8, 2016 at 3:57 AM, Evgeni Burovski wrote: > -- Forwarded message -- > From: Evgeni Burovski > Date: Mon, Feb 8, 2016 at 11:56 AM > Subject: Re: [Numpy-discussion] Multi-distribution Linux wheels - please test > To: Discussion of Numerical Python > > > On Sat, Feb 6,

Re: [Numpy-discussion] [SciPy-Dev] Multi-distribution Linux wheels - please test

Hi, On Mon, Feb 8, 2016 at 3:29 AM, Daπid wrote: > > On 6 February 2016 at 21:26, Matthew Brett wrote: >> >> >> pip install -f https://nipy.bic.berkeley.edu/manylinux numpy scipy >> python -c 'import numpy; numpy.test()' >> python -c 'import scipy; scipy.test()' > > > > All the tests pass on my

Re: [Numpy-discussion] Linking other libm-Implementation

On 02/08/2016 06:36 PM, Nathaniel Smith wrote: > On Feb 8, 2016 3:04 AM, "Nils Becker" > wrote: >> > [...] >> Very superficial benchmarks (see below) seem devastating for gnu libm. > It seems that openlibm (compiled with gcc -mtune=native -O3) performs > really well

Re: [Numpy-discussion] Linking other libm-Implementation

On Feb 8, 2016 3:04 AM, "Nils Becker" wrote: > [...] > Very superficial benchmarks (see below) seem devastating for gnu libm. It seems that openlibm (compiled with gcc -mtune=native -O3) performs really well and intels libm implementation is the best (on my intel CPU). I did not check the accuracy

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

On 02/08/2016 05:23 PM, Daπid wrote: > > On 8 February 2016 at 16:19, Olivier Grisel > wrote: > > > > OPENBLAS_CORETYPE=Nehalem python3 -c "import numpy as np; from scipy > import linalg; linalg.eigh(np.random.randn(200, 200))" > > So this is an is

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

On 8 February 2016 at 16:19, Olivier Grisel wrote: > > > OPENBLAS_CORETYPE=Nehalem python3 -c "import numpy as np; from scipy > import linalg; linalg.eigh(np.random.randn(200, 200))" > > So this is an issue with the architecture detection of OpenBLAS. I am seeing the same problem on a native Li

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

Note that the above segfault was found in a VM (docker-machine virtualbox guest VM launched on a OSX host). The DYNAMIC_ARCH feature of OpenBLAS detects an Sandybridge core (using https://gist.github.com/ogrisel/ad4e547a32d0eb18b4ff). Here are the flags of the CPU visible from inside the docker co

[Numpy-discussion] Fwd: Multi-distribution Linux wheels - please test

-- Forwarded message -- From: Evgeni Burovski Date: Mon, Feb 8, 2016 at 11:56 AM Subject: Re: [Numpy-discussion] Multi-distribution Linux wheels - please test To: Discussion of Numerical Python On Sat, Feb 6, 2016 at 8:26 PM, Matthew Brett wrote: > Hi, > > As some of you may ha

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

On 6 February 2016 at 21:26, Matthew Brett wrote: > > pip install -f https://nipy.bic.berkeley.edu/manylinux numpy scipy > python -c 'import numpy; numpy.test()' > python -c 'import scipy; scipy.test()' > All the tests pass on my Fedora 23 with Python 2.7, but it seems to be linking to the syst

Re: [Numpy-discussion] Linking other libm-Implementation

> The npy_math functions are used if otherwise unavailable OR if someone > has at some point noticed that say glibc 2.4-2.10 has a bad quality > tan (or whatever) and added a special case hack that checks for those > particular library versions and uses our built-in version instead. > It's not the

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

I found another problem by running the tests of scikit-learn: python3 -c "import numpy as np; from scipy import linalg; linalg.eigh(np.random.randn(200, 200))" Segmentation fault Note that the following works: python3 -c "import numpy as np; np.linalg.eigh(np.random.randn(200, 200))" Also note

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

I used docker to run the numpy tests on base/archlinux. I had to pacman -Sy python-pip openssl and gcc (required by one of the numpy tests): ``` Ran 5621 tests in 34.482s OK (KNOWNFAIL=4, SKIP=9) ``` Everything looks fine. -- Olivier ___ NumPy-Discuss

Re: [Numpy-discussion] Multi-distribution Linux wheels - please test

On Feb 7, 2016 11:49 PM, "Matthew Brett" wrote: > > Hi Nadav, > > On Sun, Feb 7, 2016 at 11:13 PM, Nathaniel Smith wrote: > > (This is not relevant to the main topic of the thread, but FYI I think the > > recarray issues are fixed in 1.10.4.) > > > > On Feb 7, 2016 11:10 PM, "Nadav Horesh" wrote