Mailman 3 September 2005 - SciPy-Dev

Release of SciPy Core 0.4 (Beta)
by Travis Oliphant 24 Nov '05

24 Nov '05

This is to announce the release of SciPy Core 0.4.X (beta) It is available at sourceforge which you can access by going to http://numeric.scipy.org Thanks to all who helped me with this release, especially Robert Kern Pearu Peterson Now, let's start getting this stable.... -Travis Oliphant

9 29

numarray weave commit? weave maintainer?
by Todd Miller 07 Oct '05

07 Oct '05

I have a patch for weave for numarray which passes all of the default self-tests. In doing my final checkout, I noticed that weave.test(level=10) has some errors and eventually segfaults... for Numeric. This was on RHEL3 with Python-2.4.1. Is anyone actively maintaining weave? Does anyone have a problem with me committing changes which enable numarray to pass weave.test() even though the level=10 tests are still showing problems for both numarray and Numeric? Todd

3 4

Re: [SciPy-user] Release of SciPy Core 0.4 (Beta)
by Pearu Peterson 30 Sep '05

30 Sep '05

On Fri, 30 Sep 2005, Rob Managan wrote: > OK, I am giving this a go. > > I seem to be not setting a flag about some math functions availability. > > Here are the details (aorry about the length of it but I snipped a lot!): > > OSX 10.3.9, Python 2.4.1 > > Installed g77v3.4-bin.tar.gz from http://hpc.sourceforge.net/ as described > into /usr/local/... > Installed fftw-3.0.1-fma.tar.gz from http://www.fftw.org/download.html into > ~/Documents/local/... where I have other libraries I have installed. > > Got scipy_core-0.4.1.tar.gz from > http://sourceforge.net/project/showfiles.php?group_id=1369&package_id=6222, > wanted to try out the new replacement for Numeric > > tar -zxvf scipy_core-0.4.1.tar.gz > cd scipy_core-0.4.1 > python setup.py build > gcc: build/src/scipy/base/src/umathmodule.c > In file included from build/src/scipy/base/src/umathmodule.c:8: > scipy/base/include/scipy/arrayobject.h:84: warning: redefinition of `ushort' > /usr/include/sys/types.h:82: warning: `ushort' previously declared here > scipy/base/include/scipy/arrayobject.h:85: warning: redefinition of `uint' > /usr/include/sys/types.h:83: warning: `uint' previously declared here > build/src/scipy/base/src/umathmodule.c: In function `nc_floor_quotl': > build/src/scipy/base/src/umathmodule.c:1257: warning: implicit declaration of > function `floorl' > build/src/scipy/base/src/umathmodule.c: In function `nc_sqrtl': > build/src/scipy/base/src/umathmodule.c:1269: warning: implicit declaration of > function `sqrtl' > ... > build/src/scipy/base/__umath_generated.c:171: error: initializer element is > not constant > build/src/scipy/base/__umath_generated.c:171: error: (near initialization for > `arccosh_data[2]') Detection of the availability of long functions is not working properly in scipy_core-0.4.1. This is fixed in svn. So, try newcore from svn. On windows XP box with latest mingw32 I have experienced similar problems with float versions of inverse hyperbolic functions: it appears that while asinhf is defined then atanhf is not, I am in a middle of debugging process with it right now.. Pearu

1 0

Supported Python versions?
by cookedm＠physics.mcmaster.ca 30 Sep '05

30 Sep '05

Currently, INSTALL.txt says we support Python 2.1, 2.2, and 2.3 (and presumably 2.4 :). How useful is 2.1 and 2.2 support? Does anybody test on these? I'd say that 2.3 support is still important, but if no one's checking for 2.1 or 2.2 compatibility, should we bother claiming they're suppported? Right now, for instance, scipy.base won't compile with 2.2. -- |>|\/|< /--------------------------------------------------------------------------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |cookedm(a)physics.mcmaster.ca

2 1

Install of scipy core for current scipy users
by Travis Oliphant 30 Sep '05

30 Sep '05

If you are a current user of scipy and want to try out the new scipy core. You can do so. However, the default install will change four __init__.py files on your system (which will probably "break" the rest of scipy). Hopefully we will get scipy as a whole to work with the new system shortly. There has also been talk of putting together a simple install to fixup the __init__ files so that old scipy and new scipy_core can live together peacefully (anyone who can help with that is welcomed). scipy\__init__.py scipy\linalg\__init__.py scipy\fftpack\__init__.py scipy\stats\__init__.py are the affected files. The ones from scipy can just be copied back, but then you won't get the functions from new scipy. -Travis

1 0

Re: [SciPy-user] Gamma distribution questions
by Travis Oliphant 30 Sep '05

30 Sep '05

Stephen Walton wrote: > Robert Kern wrote, way back on September 8: > >> Currently, the fit() method of distributions is broken. There's a >> problem with the way it passes arguments to the nnlf() method; that >> problem seems to apply to all distributions. >> > I actually fixed this, kind of, some time ago. See > > > P.S. Does anyone read the Bug Tracker entries at scipy.org? My > morestats.py fix is over three months old. I don't read it regularly -- I read email much more. So make sure to post an announcement to this list. Also, I have been pre-occupied with the new core system. Also, the move to svn put a big delay on placing any fixes into scipy as several people lost write access. So, don't be discouraged. There have been some growing pains this summer. We also need more people who are willing to have write access to the actual source tree. Any takers? (I won't just let anybody make changes, but if you've already contributed to SciPy in some fashion, you are a likely candidate...) -Travis O.

6 5

Release going to happen tonight.
by Travis Oliphant 30 Sep '05

30 Sep '05

With Pearu's commits, I'm about ready to make a beta release. Now, where do I place it? I'll probably put it on the sourceforge site as well as make a link on numeric.scipy.org. What do you all think? -Travis P.S. I resolved my rpm building error by deleting an old buildroot tree in /var/tmp. If anybody else has the same problem, you might look into deleting old copies of the rpm buildroot tree. Now, I have shiny rpm's of the distribution... -Travis

6 9

status of newcore and f2py
by Pearu Peterson 30 Sep '05

30 Sep '05

Hi, When forcing f2py to use newcore, that is, when changing #include "Numeric/arrayobject.h" to #include "scipy/arrayobject.h" in newcore/scipy/f2py2e/src/fortranobject.h, then I get the folloing messages /tmp/tmpqynjjs/src/fortranobject.c: In function 'fortran_setattr': /tmp/tmpqynjjs/src/fortranobject.c:233: warning: implicit declaration of function '_PyArray_multiply_list' /tmp/tmpqynjjs/src/fortranobject.c: In function 'copy_ND_array': /tmp/tmpqynjjs/src/fortranobject.c:980: warning: passing argument 2 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:980: warning: passing argument 3 of 'cast' makes integer from pointer without a cast /tmp/tmpqynjjs/src/fortranobject.c:980: warning: passing argument 4 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:980: warning: passing argument 5 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1004: warning: passing argument 2 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1004: warning: passing argument 3 of 'cast' makes integer from pointer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1004: warning: passing argument 4 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1004: warning: passing argument 5 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1023: warning: passing argument 2 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1023: warning: passing argument 3 of 'cast' makes integer from pointer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1023: warning: passing argument 4 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c:1023: warning: passing argument 5 of 'cast' makes pointer from integer without a cast /tmp/tmpqynjjs/src/fortranobject.c: At top level: /usr/local/include/python2.3/scipy/__multiarray_api.h:681: warning: 'import_array' defined but not used when compiling fortranobject.c and when trying to import the corresponding extension module, I get >>> import foo Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: ./foo.so: undefined symbol: _PyArray_multiply_list So, we need to have a newcore replacement for _PyArray_multiply_list. Is there anything available already? Pearu

2 2

Help with error
by Travis Oliphant 29 Sep '05

29 Sep '05

Can anybody with experience on building RPMS help me. I tried bdist_rpm, but get the following error: error: Installed (but unpackaged) file(s) found: /usr/lib/python2.4/site-packages/atlas_version.so RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib/python2.4/site-packages/atlas_version.so error: command 'rpmbuild' failed with exit status 1 I don't know how to get rpm to package this file -Travis

3 4

RE: [SciPy-dev] Re: [SciPy-user] Gamma distribution questions
by Charles Harris 29 Sep '05

29 Sep '05

Travis, I used to have access, but my password seems to have lapsed. There are a few cleanups and comments I could make to those small parts of Scipy I contributed. I also extended the sort functions in numarray and might look into porting them to the new core. Chuck -----Original Message----- From: scipy-dev-bounces(a)scipy.net on behalf of Travis Oliphant Sent: Thu 9/29/2005 12:56 PM To: SciPy Users List; SciPy Developers List Subject: [SciPy-dev] Re: [SciPy-user] Gamma distribution questions Stephen Walton wrote: > Robert Kern wrote, way back on September 8: > >> Currently, the fit() method of distributions is broken. There's a >> problem with the way it passes arguments to the nnlf() method; that >> problem seems to apply to all distributions. >> > I actually fixed this, kind of, some time ago. See > > > P.S. Does anyone read the Bug Tracker entries at scipy.org? My > morestats.py fix is over three months old. I don't read it regularly -- I read email much more. So make sure to post an announcement to this list. Also, I have been pre-occupied with the new core system. Also, the move to svn put a big delay on placing any fixes into scipy as several people lost write access. So, don't be discouraged. There have been some growing pains this summer. We also need more people who are willing to have write access to the actual source tree. Any takers? (I won't just let anybody make changes, but if you've already contributed to SciPy in some fashion, you are a likely candidate...) -Travis O. _______________________________________________ Scipy-dev mailing list Scipy-dev(a)scipy.net http://www.scipy.net/mailman/listinfo/scipy-dev

1 0