Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Matthew Brett
Hi, On Thu, Nov 17, 2016 at 3:24 PM, Matti Picus wrote: > Congrats to all on the release.Two questions: > > Is there a guide to building standard wheels for NumPy? I don't think so - there is a repository that we use to build the wheels, that has the Windows, OSX and manyllinux recipes for the s

Re: [Numpy-discussion] Status of NAs for integer arrays

2016-11-18 Thread Ralf Gommers
On Fri, Nov 18, 2016 at 8:43 PM, Dmitrii Izgurskii wrote: > Hi, > > I would like to know where I can follow the progress of what's being done > on implementing missing values in integer arrays. Some threads I found are > from 2012. Is really nothing being done on this issue? > Not that I'm aware

Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Ralf Gommers
On Fri, Nov 18, 2016 at 9:08 PM, Matthew Brett wrote: > Hi, > > On Thu, Nov 17, 2016 at 3:24 PM, Matti Picus > wrote: > > Congrats to all on the release.Two questions: > > > > Is there a guide to building standard wheels for NumPy? > > I don't think so - there is a repository that we use to buil

[Numpy-discussion] ANN: xtensor and xtensor-python

2016-11-18 Thread Sylvain Corlay
Hi all, We are pleased to announce the release of the xtensor library and its python bindings xtensor-python , by Johan Mabille (@JohanMabille) and Sylvain Corlay (@SylvainCorlay).

Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Peter Cock
I have a related question to Matti's, Do you have any recommendations for building standard wheels for 3rd party Python libraries which use both the NumPy Python and C API? e.g. Do we need to do anything special given the NumPy C API itself is versioned? Does it matter compiler chain should we us

Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Nathan Goldbaum
Since the NumPy API is forwards compatible, you should use the oldest version of NumPy you would like to support to build your wheels with. The wheels will then work with any future NumPy versions. On Fri, Nov 18, 2016 at 9:30 AM Peter Cock wrote: > I have a related question to Matti's, > > Do y

Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Peter Cock
Thanks Nathan, That makes sense (compile using the oldest version of NumPy we wish to support). The information on https://github.com/MacPython/numpy-wheels will probably be very useful too (I've been meaning to try out appveyor at some point for Windows builds/testing). Regards, Peter On Fri,

Re: [Numpy-discussion] NumPy 1.12.0b1 released

2016-11-18 Thread Nathaniel Smith
On Nov 18, 2016 01:14, "Ralf Gommers" wrote: > > > > On Fri, Nov 18, 2016 at 9:08 PM, Matthew Brett wrote: >> >> Hi, >> >> On Thu, Nov 17, 2016 at 3:24 PM, Matti Picus wrote: >> > Congrats to all on the release.Two questions: >> > >> > Is there a guide to building standard wheels for NumPy? >> >

[Numpy-discussion] PyPy wheels (was: NumPy 1.12.0b1 released)

2016-11-18 Thread Ralf Gommers
On Sat, Nov 19, 2016 at 5:24 AM, Nathaniel Smith wrote: > Another thing to think about is that 1.12 on pypy won't pass its test > suite (though it's close), and we're not yet testing new PRs on pypy, so no > guarantees about 1.13 yet. I think on balance these probably aren't reasons > *not* to up

Re: [Numpy-discussion] PyPy wheels (was: NumPy 1.12.0b1 released)

2016-11-18 Thread Nathaniel Smith
On Nov 18, 2016 3:30 PM, "Ralf Gommers" wrote: > > > > On Sat, Nov 19, 2016 at 5:24 AM, Nathaniel Smith wrote: >> >> Another thing to think about is that 1.12 on pypy won't pass its test suite (though it's close), and we're not yet testing new PRs on pypy, so no guarantees about 1.13 yet. I think

Re: [Numpy-discussion] PyPy wheels (was: NumPy 1.12.0b1 released)

2016-11-18 Thread Ralf Gommers
On Sat, Nov 19, 2016 at 2:53 PM, Nathaniel Smith wrote: > On Nov 18, 2016 3:30 PM, "Ralf Gommers" wrote: > > > > > > > > On Sat, Nov 19, 2016 at 5:24 AM, Nathaniel Smith wrote: > >> > >> Another thing to think about is that 1.12 on pypy won't pass its test > suite (though it's close), and we're