On 30 January 2014 10:56, Paul Moore wrote:
>> Here we go: https://github.com/numpy/numpy/issues/4245
>>
> Thanks. I've added the installation details and output from a test run.
That bug report was just closed blaming a distutils issue which
apparently numpy aren't going to work around :-( I don
Thanks. I've added the installation details and output from a test run.
Paul
On 30 January 2014 10:25, David Cournapeau wrote:
>
>
>
> On Thu, Jan 30, 2014 at 10:20 AM, Paul Moore wrote:
>>
>> On 30 January 2014 09:12, David Cournapeau wrote:
>> >
>> > On Thu, Jan 30, 2014 at 7:50 AM, Paul Moor
On Thu, Jan 30, 2014 at 10:20 AM, Paul Moore wrote:
> On 30 January 2014 09:12, David Cournapeau wrote:
> >
> > On Thu, Jan 30, 2014 at 7:50 AM, Paul Moore wrote:
> >>
> >> On 29 January 2014 22:50, David Cournapeau wrote:
> >> >> i.e. it would be nice if anyone setup to build C extensions cou
On 30 January 2014 09:12, David Cournapeau wrote:
>
> On Thu, Jan 30, 2014 at 7:50 AM, Paul Moore wrote:
>>
>> On 29 January 2014 22:50, David Cournapeau wrote:
>> >> i.e. it would be nice if anyone setup to build C extensions could "just
>> >> build numpy".
>> >
>> > This has always been possib
On Thu, Jan 30, 2014 at 7:50 AM, Paul Moore wrote:
> On 29 January 2014 22:50, David Cournapeau wrote:
> >> i.e. it would be nice if anyone setup to build C extensions could "just
> >> build numpy".
> >
> > This has always been possible, and if not, that's certainly considered
> as a
> > bug (I
On 29 January 2014 22:50, David Cournapeau wrote:
>> i.e. it would be nice if anyone setup to build C extensions could "just
>> build numpy".
>
> This has always been possible, and if not, that's certainly considered as a
> bug (I would be eager to fix).
I don't know if you saw my comment earlier
On Wed, Jan 29, 2014 at 10:52 PM, Donald Stufft wrote:
> I don’t see any reason why SSE couldn’t be added as tags in the Wheel
> filename fwiw.
>
You still need to decide when to install what, but I would be interested in
talking more about that part.
>
> That doesn’t help for things like MKL
I don’t see any reason why SSE couldn’t be added as tags in the Wheel filename
fwiw.
That doesn’t help for things like MKL though.
On Jan 29, 2014, at 5:50 PM, David Cournapeau wrote:
>
>
>
> On Wed, Jan 29, 2014 at 10:27 PM, Chris Barker wrote:
> On Wed, Jan 29, 2014 at 2:04 PM, David Cou
On Wed, Jan 29, 2014 at 10:27 PM, Chris Barker wrote:
> On Wed, Jan 29, 2014 at 2:04 PM, David Cournapeau wrote:
>
>> I think the SSE issue is a bit of a side discussion: most people who care
>> about performance already know how to install numpy. What we care about
>> here are people who don't ca
On Wed, Jan 29, 2014 at 2:04 PM, David Cournapeau wrote:
> I think the SSE issue is a bit of a side discussion: most people who care
> about performance already know how to install numpy. What we care about
> here are people who don't care so much about fast eigenvalue decomposition,
> but want to
On Sun, Jan 26, 2014 at 12:29 AM, Nick Coghlan wrote:
> Paul's position exactly mirrors my own - I an perfectly fine with the
> recommended advice to scientific users continuing to be "NumPy doesn't
> officially support pip and virtualenv because of the way it is built and
> installed, so you wil
On Sat, Jan 25, 2014 at 4:29 PM, Nick Coghlan wrote:
> To put the "but what if the user doesn't have SSE2 support?" concern in
> context, it should only affect Intel users with CPUs older than a Pentium 4
> (released 2001), and AMD users with a CPU older than an Opteron or Athlon
> 64 (both relea
On 29 January 2014 18:06, Paul Moore wrote:
> On 29 January 2014 05:06, Chris Barker wrote:
>> This isn't just for users of the SciPy Stack -- there are LOT of use-cases
>> for just numpy by itself. Not that I don't want folks to have easy access of
>> the rest of the stack as well -- just sayin'
On 29 January 2014 05:06, Chris Barker wrote:
> This isn't just for users of the SciPy Stack -- there are LOT of use-cases
> for just numpy by itself. Not that I don't want folks to have easy access of
> the rest of the stack as well -- just sayin'
Agreed - my main use for NumPy is with Pandas fo
Paul's position exactly mirrors my own - I an perfectly fine with the
recommended advice to scientific users continuing to be "NumPy doesn't
officially support pip and virtualenv because of the way it is built and
installed, so you will have to get one of the curated scientific stacks,
bootstrap co
On 25 January 2014 23:36, Vinay Sajip wrote:
>> Those people currently either use the wininst installers (which I'm
>> *not* advocating that we remove) or they use virtualenvs, and have the
>> view that they have to at a minimum jump through some hoops to get
>> numpy to work.
>
> I don't know if
On Sat, 25/1/14, Paul Moore wrote:
> Wheels are an improvement over the wininst status quo because they
> support virtualenvs. So I want to see numpy wheels available, because
> that would be a significant step in making people aware of some of the
>
On 25 January 2014 21:56, Oscar Benjamin wrote:
> I'll try to summarise your take on this: You would like to take the
> time to ensure that Python packaging is done properly. That may mean
> that some functionality isn't available for some time, but you think
> that it's better to "get it right" t
On 24 January 2014 10:18, Nick Coghlan wrote:
>
> On 24 Jan 2014 19:41, "Paul Moore" wrote:
>>
>> On 24 January 2014 00:17, Oscar Benjamin
>> wrote:
>> > You need to bear in mind that people currently have a variety of ways
>> > to install numpy on Windows that do work already without limitation
On 25 January 2014 21:33, Oscar Benjamin wrote:
> Last time I tried with mingw it worked (I've since departed the
> Windows world). I think official numpy binaries for Windows are built
> with mingw (Christoph uses MSVC though).
That may well be the case, but MSVC (Express or full) is the
"standa
On 24 January 2014 22:40, Paul Moore wrote:
> On 24 January 2014 22:21, Chris Barker wrote:
>> well, numpy _should_ build out of the box with nothing special if you are
>> set up to build regular extensions. I understand that a lto f Windows users
>> are not set up to build extensions at all, but
On Fri, Jan 24, 2014 at 2:40 PM, Paul Moore wrote:
> So no, numpy does not build out of the box. Ah well.
>
Darn -- it used to, and it should. It has shipped for years with an "LAPACK
light", and shouldn't need any fortran. It used to not even look for LAPACK
with a default configuration.
But I
On 24 January 2014 22:21, Chris Barker wrote:
> well, numpy _should_ build out of the box with nothing special if you are
> set up to build regular extensions. I understand that a lto f Windows users
> are not set up to build extensions at all, but tehy ar presumably used to
> getting "compiler no
On Fri, Jan 24, 2014 at 2:18 AM, Nick Coghlan wrote:
> In return, as Paul points out, it becomes substantially easier for people
> that *aren't* wholly invested in the scientific Python stack to try it out
> with their regular tools, rather than having to completely change how they
> work with Py
On 24 January 2014 20:09, Matthew Iversen wrote:
> Might I suggest you could upload some wheels (both windows and linux) to
> testpypi, which afaik is pretty much made for this purpose?
Well, Windows and Mac OS X - we don't allow PyPI wheels for Linux at
the moment (since it turns out the compati
Might I suggest you could upload some wheels (both windows and linux) to
testpypi, which afaik is pretty much made for this purpose?
https://wiki.python.org/moin/TestPyPI
People can easily install then with e.g. `pip install --index-url
https://testpypi.python.org/pypi numpy`, and see what tends
On 24 Jan 2014 19:41, "Paul Moore" wrote:
>
> On 24 January 2014 00:17, Oscar Benjamin
wrote:
> > You need to bear in mind that people currently have a variety of ways
> > to install numpy on Windows that do work already without limitations
> > on CPU instruction set. Most numpy users will not ge
On 24 January 2014 00:17, Oscar Benjamin wrote:
> You need to bear in mind that people currently have a variety of ways
> to install numpy on Windows that do work already without limitations
> on CPU instruction set. Most numpy users will not get any immediate
> benefit from the fact that "it work
On Jan 23, 2014, at 4:17 PM, Oscar Benjamin wrote:
> On 23 January 2014 23:58, Nick Coghlan wrote:
>>
>> I really think that's our best near term workaround - still room for
>> improvement, but " pip install numpy assumes SSE2" is a much better
>> situation than "pip install numpy doesn't work
On 23 January 2014 23:58, Nick Coghlan wrote:
>
> I really think that's our best near term workaround - still room for
> improvement, but " pip install numpy assumes SSE2" is a much better
> situation than "pip install numpy doesn't work on Windows".
Is it? Do you have any idea what proportion of
On 24 Jan 2014 08:03, "Chris Barker" wrote:
>
> On Thu, Jan 23, 2014 at 12:25 PM, Thomas Heller
wrote:
>>
>> Did I say this before? I would suggest that numpy develops a way
>> where all the SSE binary variations would be installed, and the
>> appropriate ones be loaded at runtime, depending on
On Thu, Jan 23, 2014 at 12:25 PM, Thomas Heller wrote:
> Did I say this before? I would suggest that numpy develops a way
> where all the SSE binary variations would be installed, and the
> appropriate ones be loaded at runtime, depending on the user's CPU
> capabilities. This would also allow
On 24 January 2014 06:25, Thomas Heller wrote:
> Am 23.01.2014 19:52, schrieb Ralf Gommers:
>> On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
>> mailto:oscar.j.benja...@gmail.com>> wrote:
>>
>> On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>> >
>> > The official numpy
Am 23.01.2014 19:52, schrieb Ralf Gommers:
On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
mailto:oscar.j.benja...@gmail.com>> wrote:
On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>
> The official numpy installer uses some complex magic to select the
> right b
On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
wrote:
> On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
> >
> > The official numpy installer uses some complex magic to select the
> > right binaries based on your CPU, and this means that the official
> > numpy "superpack" wininst files
On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>
> The official numpy installer uses some complex magic to select the
> right binaries based on your CPU, and this means that the official
> numpy "superpack" wininst files don't convert (at least I don't think
> they do, it's a while si
Am 23.01.2014 13:16, schrieb Paul Moore:
On 23 January 2014 11:48, Thomas Heller wrote:
Is there a solution to this? I've seen that the wheel tool can convert
bdist_wininst installers into wheels - does this work for the packages
I mentioned above? Do we have to build or convert to wheel thos
On 23 January 2014 11:48, Thomas Heller wrote:
> After having used and built bdist_wininst installers for years (well, I
> should say decades) I have recently started playing with pip.
Thanks for trying this - it's really useful to have a newcomer's
perspective to the pip experience.
> However,
After having used and built bdist_wininst installers for years (well, I
should say decades) I have recently started playing with pip.
In theory, it is a grat solution. Respects virtual environments
(although I haven't tested them yet), allows to freeze to a requirements
file, and so on.
It woul
39 matches
Mail list logo
