On Mon, May 19, 2014 at 1:01 AM, Toby St Clere Smithe m...@tsmithe.netwrote:
Hi,
I'm sure you're all aware of this,
I wasn't actually.
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
Hi Ralf,
Ralf Gommers ralf.gomm...@gmail.com 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
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 m...@tsmithe.net wrote:
Hi Ralf,
Ralf Gommers ralf.gomm...@gmail.com writes:
I wasn't actually.
Well, I'm glad I could be of service, I guess. Should I report this as
Daniel Holth dho...@gmail.com writes:
Just build a wheel first. Then numpy is installed twice but only built once.
Sure -- but why isn't this automatic? This solution is a bit of a hack
around what seems a needless inefficiency!
Best,
Toby
On May 24, 2014 12:16 PM, Toby St Clere Smithe
From: Daniel Holth dho...@gmail.com
Just build a wheel first. Then numpy is installed twice but only built once.
Isn't that just papering over the cracks?
Regards,
Vinay Sajip
___
Distutils-SIG maillist - Distutils-SIG@python.org
The plan is that pip will cache builds automatically in the future.
Generally build requirements should be kept separate from install
requirements.
On May 24, 2014 12:25 PM, Toby St Clere Smithe m...@tsmithe.net wrote:
Daniel Holth dho...@gmail.com writes:
Just build a wheel first. Then numpy
On May 24, 2014, at 12:20 PM, Toby St Clere Smithe m...@tsmithe.net wrote:
Daniel Holth dho...@gmail.com writes:
Just build a wheel first. Then numpy is installed twice but only built once.
Sure -- but why isn't this automatic? This solution is a bit of a hack
around what seems a needless
On May 24, 2014, at 12:23 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
From: Daniel Holth dho...@gmail.com
Just build a wheel first. Then numpy is installed twice but only built once.
Isn't that just papering over the cracks?
Yes, but all the problems can't be solved at once
Daniel Holth dho...@gmail.com writes:
The plan is that pip will cache builds automatically in the future.
Generally build requirements should be kept separate from install
requirements.
This sounds like the best policy. I'm glad it's on the roadmap -- I
presume this means I do not need to
Pull requests implementing the feature are also welcome.
On May 24, 2014 12:54 PM, Toby St Clere Smithe m...@tsmithe.net wrote:
Daniel Holth dho...@gmail.com writes:
The plan is that pip will cache builds automatically in the future.
Generally build requirements should be kept separate from
Daniel Holth dho...@gmail.com writes:
Pull requests implementing the feature are also welcome.
Well, of course. Depending on how my work goes, you may be lucky.
Cheers,
Toby
On May 24, 2014 12:54 PM, Toby St Clere Smithe m...@tsmithe.net wrote:
Daniel Holth dho...@gmail.com writes:
The
On 25 May 2014 02:54, Toby St Clere Smithe m...@tsmithe.net wrote:
Daniel Holth dho...@gmail.com writes:
The plan is that pip will cache builds automatically in the future.
Generally build requirements should be kept separate from install
requirements.
This sounds like the best policy.
12 matches
Mail list logo
