I'm trying to track down a numerical discrepancy in our proejct. We
noticed that a certain set of results are different having upgraded from
scipy 0.6.0 to 0.7.0.
The following item from the Scipy change-log is our current number-one
suspect. Could anybody who knows suggest what was actually
I've noticed that with scipy 0.7.0 + numpy 1.2.1, an importing the
factorial function from the scipy module always seems to fail when scipy
is installed as a zipped ,egg file. When the project is installed as
an unzipped directory it works fine.
Is there any reason why this function should not
I don't think numpy/scipy are zip safe, the numpy packageloader uses
os.path to find files.
Evidently! :-)
But the strange thing is that all this worked fine with Scipy 0.6.0 -
it's only since 0.7.0 was released that this started going wrong.
Sal
Disclaimer CALYON UK:
This email does not
I have a 0d array that looks like this:
myarray = array( 0.1234 )
This generates a TypeError:
myarray[0]
I can get it's number using a hack like this... but it looks kind of
wrong:
myval = myarray + 0.0
There must be a better way to do it, right? All I want is the correct
way to return the
Yes,
Thanks for all your support, it works a treat. My conclusion is that the
.exe release for Windows are sufficient for our needs.
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Charles R
Harris
Sent: 17
You actually need the package unpacked to use scipy.weave and make C
extensions which use Numpy's .h files.
We have found that Numpy + Scipy are perfectly zip-safe for users but
not for developers.
-Original Message-
From: numpy-discussion-boun...@scipy.org
I just installed the latest stable mingw, and made sure that the mingw
bin directory is in my PATH. I used the command you suggested and got
the following output:
http://pastebin.com/m4aea512c
Any suggestions as to what I might be doing wrong?
I'm using standard cpython 2.4.4 from Python.org
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Hi Sal,
On Wed, Apr 15, 2009 at 1:03 PM, Fadhley Salim
fadhley.sa...@uk.calyon.com wrote:
http://projects.scipy.org/numpy/ticket/1086
I filed this under numpy since that's
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
On Thu, Apr 16, 2009 at 00:45, Gael Varoquaux
gael.varoqu...@normalesup.org wrote:
On Wed, Apr 15, 2009 at 07:33:48PM +0100, Fadhley Salim wrote:
We deploy on a very large number of computers in 5
As I said before we have a very big set up. The problem is not the
difficulty in making eggs. Eggs are very easy things to make if you can
make the C++ compile first.
Setuptools is a very good and stable project whose purpose is to help
automate very large deployments of Python dependancies.
Eggs are still beneficial:
* People who do not have access to PyPi can still use it (think banks)
* If you can build eggs easily then so can people like me... it becomes
easy to produce optimized eggs for all our Xeon processors.
* Deploying an egg is nothing more than copying a file to the
I've been asked to provide Numpy Scipy as python egg files.
Unfortunately Numpy and Scipy do not make official releases of their
product in .egg form for a Win32 platform - that means if I want eggs
then I have to compile them myself.
At the moment my employer provides Visual Studio.Net 2003,
compiling them
yourself will lead to worse performance, as David provides atlas with numpy and
scipy).
Matthieu
2009/4/15 Fadhley Salim fadhley.sa...@uk.calyon.com:
I'm compiling for Python 2.4, so I guess that means that I'm never going to
be able to use anything more than visual studio 2003?
What
!
:-)
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Thomas Heller
Sent: 15 April 2009 18:48
To: numpy-discussion@scipy.org
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Fadhley Salim schrieb:
So what is the official
Mingw is used to compile numpy and scipy AFAIK.
So if I just grab Mingw I should be able to compile the latest stuff
with no problems? Will that work perfectly with my standard Python.org
Cpython distribution?
Why is exe files a problem ?
We deploy on a very large number of computers in 5
...@scipy.org] On Behalf Of Andrew Straw
Sent: 15 April 2009 19:31
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Fadhley Salim wrote:
Thomasm,
What want is the current latest Numpy as a win32 .egg file for Python
2.4.4. I'm not bothered how I get
...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Charles R
Harris
Sent: 15 April 2009 19:32
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
On Wed, Apr 15, 2009 at 11:58 AM, Fadhley Salim
fadhley.sa...@uk.calyon.com wrote
, 2009 at 12:37 PM, Fadhley Salim
fadhley.sa...@uk.calyon.com wrote:
Chuck,
I'm not all that familiar with the bug reporting process but if
you were to point me to the relevant bug tracker I'd be delighted to
file an issue. If I could get somebody to fix this upstream I'd
Is there a way to make a multi-version egg from the Numpy source code
(supplied from sourceforge).
Ideally I'd like to create an automated process that allows me to
quickly make a Win32 egg any time a new release of Numpy comes out so
that my team can test it and adjust our project's
Can one of the Numpy experts explain what this means and how I might be
able to solve it? I'm trying to compile Numpy 1.2 - I just zipped the
tar file from Sourceforge.
Thanks!
compiling C sources
creating build\temp.win32-2.4\Release\numpy\random
creating
20 matches
Mail list logo
