Just build a wheel first. Then numpy is installed twice but only built once. On May 24, 2014 12:16 PM, "Toby St Clere Smithe" <[email protected]> wrote:
> Hi Ralf, > > Ralf Gommers <[email protected]> writes: > > I wasn't actually. > > Well, I'm glad I could be of service, I guess. Should I report this as a > bug? > > >> but I wonder if there's any progress > >> for me to be aware of. I've got an extension that I build with > >> distutils. It requires numpy both to build and to run, so I have numpy > >> in both setup_requires and install_requires. Yet setup.py builds numpy > >> twice -- once for the build stage, and then again on installation. This > >> seems inefficient to me -- why not just build it once? Is this by > >> design? > >> > > > > Seems fairly inefficient, so I'd guess it's not by design. > > Indeed. > > > Note that if numpy is already installed, you may want to avoid adding the > > *_requires arguments in order not to silently upgrade or break the > > installed numpy. Something like > > https://github.com/scipy/scipy/pull/3566/files > > This is good advice, but what about the cases in which the build machine > is not the installation machine? I already have a versioned dependency, > which will on each possible machine (trivially) either be satisfied or > not, and if it's not, then it should be. > > Cheers, > > Toby > > > -- > Toby St Clere Smithe > http://tsmithe.net > > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
