On Sun, Sep 26, 2010 at 9:56 PM, email@example.com wrote:
On Sun, Sep 26, 2010 at 11:42 PM, firstname.lastname@example.org wrote:
On Sun, Sep 26, 2010 at 11:03 PM, Ben Longstaff email@example.com
numpy 1.5.0 (installed from numpy-1.5.0-win32-superpack-python2.6.exe
sourceforge.net) scipy 0.8.0 (installed from scipy-0.8.0-win32-superpack-python2.6.exe
sourceforge.net) python 2.6.6 (installed with ActivePython 18.104.22.168)
It's a safe combination, and the cython warning has no effect.
(Maybe a disclaimer: There's always a chance that new things show up, but I haven't heard of any problems.)
Just a side comment: ActiveState is distributing (since June)
"New packages for data centric financial modeling and scientific computing applications (available in ActivePython Business, Enterprise, and OEM Editions):
- NumPy: The fundamental library needed for financial and
scientific computing with Python
- SciPy: A suite of scientific tools for Python, depends on the
- matplotlib: A Python numerical plotting library
because of changes in US financial regulation. So maybe we get some additional testing out of it.
On Mon, Sep 27, 2010 at 12:26 PM, firstname.lastname@example.org wrote:
On Sun, Sep 26, 2010 at 9:57 PM, Ben Longstaff <
Is the warning message produced by the test script below an issue I
to address if I am to use the numpy and scipy libraries? The script
gives me the warning below on both windows 7 and vista Thanks for your time Ben
#!/path/to/python import re, string, sys from numpy import * import scipy.weave print "Hello, World!"
Warning Message C:\Python26\lib\site-packages\scipy\io\matlab\mio5.py:90: RuntimeWarning: __builtin__.file size changed, may indicate binary incompatibility from mio5_utils import VarReader5
Which numpy and scipy versions are you using? e.g. scipy.__version__ np.__version__
This looks like a warning from cython, but the versions are still binary compatible, and there shouldn't be any problems. (with all numpy except 1.4.0 and 2.x in repository)
Didn't Ralph catch the warnings on import for the released binaries? Maybe he missed one. Also, I don't recall seeing seeing that one before, not that it is necessarily a problem.