Yeah, if you build against numpy version X, and some other package builds against numpy version Y, then your packages will both with with numpy version Z if Z >= X and Z >= X
(This is speaking specifically about extensions that use the numpy C api of course -- for packages that just use the numpy python api then it doesn't matter what version you build against.) What you should also do, but currently most people don't do and we need better tooling for, is to make sure that if you build against numpy version X then your wheel should have a versioned dependency on numpy >= X. -n On Jul 21, 2016 3:44 PM, "Matthew Brett" <[email protected]> wrote: > Hi, > > On Thu, Jul 21, 2016 at 6:11 PM, Nathan Goldbaum <[email protected]> > wrote: > > Hi all, > > > > I'm curious which NumPy version we should use when generating wheels. In > > particular, will it be a problem if our dependencies use a different > NumPy > > version to build *their* wheels. > > > > It's my understanding that the NumPy ABI is forward compatible, so I > guess > > we want to build against a "sufficiently old" version? > > Right - build against the oldest version the project is compatible > with : > http://stackoverflow.com/questions/17709641/valueerror-numpy-dtype-has-the-wrong-size-try-recompiling/18369312#18369312 > > Cheers, > > Matthew > _______________________________________________ > Wheel-builders mailing list > [email protected] > https://mail.python.org/mailman/listinfo/wheel-builders >
_______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
