From pearu at scipy.org Tue Feb 10 11:46:45 2004 From: pearu at scipy.org (Pearu Peterson) Date: Tue, 10 Feb 2004 10:46:45 -0600 (CST) Subject: [SciPy-dev] "Building Scipy on Windows" notes available Message-ID: Hi all, Detailed "from scratch" notes about "Building Scipy on Windows" are available at http://cens.ioc.ee/~pearu/scipy/BUILD_WIN32.html It also contains a section on building Win32 port of Atlas libraries that seems to be a major show-stopper for Windows people, and indeed, I found it a rather sensitive subject too. Hopefully these notes will help Windows people to overcome the threshold of building Scipy themself and may enjoy most recent Scipy features from CVS. Best regards, Pearu From j_r_fonseca at yahoo.co.uk Wed Feb 11 13:08:23 2004 From: j_r_fonseca at yahoo.co.uk (=?iso-8859-1?Q?Jos=E9?= Fonseca) Date: Wed, 11 Feb 2004 18:08:23 +0000 (UTC) Subject: [SciPy-dev] How to avoid arch specific compiler flags in scipy_distutils? Message-ID: I've finally been doing some work updating the scipy & f2py debian packages and things are slowly progressing. The showstopper ATM, is the fact that the fortran sources are being compiled with architecture specific compiler flags ("-march=pentium4 -msse2 -msse ..."). I know that this is done automatically in scipy_distutils/gnufcompiler.py . Is there any non-intrusive way (i.e., from command line) to prevent that? Jos? Fonseca From pearu at scipy.org Wed Feb 11 13:20:18 2004 From: pearu at scipy.org (Pearu Peterson) Date: Wed, 11 Feb 2004 12:20:18 -0600 (CST) Subject: [SciPy-dev] How to avoid arch specific compiler flags in scipy_distutils? In-Reply-To: Message-ID: On Wed, 11 Feb 2004, Jos? Fonseca wrote: > I've finally been doing some work updating the scipy & f2py debian > packages and things are slowly progressing. Good to hear. > The showstopper ATM, is the fact that the fortran sources are being > compiled with architecture specific compiler flags ("-march=pentium4 > -msse2 -msse ..."). I know that this is done automatically in > scipy_distutils/gnufcompiler.py . Is there any non-intrusive way (i.e., > from command line) to prevent that? Yes, there is. Use build_src branch of scipy_distutils (soon it will be merged into the HEAD branch): cd cvs/scipy/scipy_core/scipy_distutils/ cvs -z7 update -r build_src Then build scipy as follows python setup.py config_fc --noarch build Pearu From j_r_fonseca at yahoo.co.uk Thu Feb 12 13:19:41 2004 From: j_r_fonseca at yahoo.co.uk (=?iso-8859-1?Q?Jos=E9?= Fonseca) Date: Thu, 12 Feb 2004 18:19:41 +0000 (UTC) Subject: [SciPy-dev] Re: How to avoid arch specific compiler flags in scipy_distutils? References: Message-ID: Pearu, On Wed, 11 Feb 2004 12:20:18 -0600 (CST), Pearu Peterson wrote: > Yes, there is. Use build_src branch of scipy_distutils (soon it will be > merged into the HEAD branch): > > cd cvs/scipy/scipy_core/scipy_distutils/ > cvs -z7 update -r build_src > > Then build scipy as follows > > python setup.py config_fc --noarch build Thanks, this did the trick. The new packages on http://jrfonseca.dyndns.org/debian/ should now be sub-architecture independent. Strangely, now when I do "import scipy" I get a warning "No module named __cvs_version__", probably due to the branch merging, but I'm not very concerned about it since you say that branch will be soon be merged in the repository. These are the remaining lintian errors & warnings: > E: python2.3-scipy: wrong-path-for-python > ./usr/lib/python2.3/site-packages/scipy/optimize/tests/test_zeros.py > #!/usr/local/lib/python > > E: python2.3-f2py: binary-without-manpage f2py2.3 > > E: python2.2-scipy: wrong-path-for-python > ./usr/lib/python2.2/site-packages/scipy/optimize/tests/test_zeros.py > #!/usr/local/lib/python > > W: python2.2-scipy: unusual-interpreter > ./usr/lib/python2.2/site-packages/scipy/special/tests/Test.py > #!/usb/bin/env > > E: python2.2-f2py: binary-without-manpage f2py2.2 > > E: python2.1-scipy: wrong-path-for-python > ./usr/lib/python2.1/site-packages/scipy/optimize/tests/test_zeros.py > #!/usr/local/lib/python > > W: python2.1-scipy: unusual-interpreter > ./usr/lib/python2.1/site-packages/scipy/special/tests/Test.py > #!/usb/bin/env > > E: python2.1-f2py: binary-without-manpage f2py2.1 If you don't mind commiting this patch below fixing the python binary paths, that would save me the trouble of patching-up afterwards: Index: Lib/optimize/tests/test_zeros.py =================================================================== RCS file: /home/cvsroot/world/scipy/Lib/optimize/tests/test_zeros.py,v retrieving revision 1.6 diff -u -r1.6 test_zeros.py --- Lib/optimize/tests/test_zeros.py 24 Oct 2003 15:15:48 -0000 1.6 +++ Lib/optimize/tests/test_zeros.py 12 Feb 2004 18:09:55 -0000 @@ -1,4 +1,4 @@ -#!/usr/local/lib/python +#!/usr/bin/env python import sys from scipy_test.testing import * Index: Lib/special/tests/Test.py =================================================================== RCS file: /home/cvsroot/world/scipy/Lib/special/tests/Test.py,v retrieving revision 1.3 diff -u -r1.3 Test.py --- Lib/special/tests/Test.py 7 Aug 2001 04:51:47 -0000 1.3 +++ Lib/special/tests/Test.py 12 Feb 2004 18:09:55 -0000 @@ -1,4 +1,4 @@ -#!/usb/bin/env python +#!/usr/bin/env python # import pickle import Numeric, cephes, RandomArray So, besides this, the remaining steps to get scipy in debian proper are: - write a manpage for f2py - wait 1-2 weeks for feedback of latest packages - get a Debian sponsor and address any concerns he may have It's much closer now than ever before (having chaco out of scipy also saved me from quite a few headaches). Jose Fonseca From pearu at scipy.org Thu Feb 12 15:13:29 2004 From: pearu at scipy.org (Pearu Peterson) Date: Thu, 12 Feb 2004 14:13:29 -0600 (CST) Subject: [SciPy-dev] Re: How to avoid arch specific compiler flags in scipy_distutils? In-Reply-To: Message-ID: Hi Jos?, On Thu, 12 Feb 2004, Jos? Fonseca wrote: > On Wed, 11 Feb 2004 12:20:18 -0600 (CST), Pearu Peterson wrote: > > Yes, there is. Use build_src branch of scipy_distutils (soon it will be > > merged into the HEAD branch): > > > > cd cvs/scipy/scipy_core/scipy_distutils/ > > cvs -z7 update -r build_src > > > > Then build scipy as follows > > > > python setup.py config_fc --noarch build > > Thanks, this did the trick. The new packages on > http://jrfonseca.dyndns.org/debian/ should now be sub-architecture independent. > > Strangely, now when I do "import scipy" I get a warning "No module named > __cvs_version__", probably due to the branch merging, but I'm not very > concerned about it since you say that branch will be soon be merged in > the repository. Yes, it turns out that whenever using branches, __cvs_version__ will not be available. Btw, the build_src branch is now in HEAD, so rm -rf scipy_distutils && cvs update -Pd is in order for whoever used build_src branch. > If you don't mind commiting this patch below fixing the python binary > paths, that would save me the trouble of patching-up afterwards: Done. > So, besides this, the remaining steps to get scipy in debian proper are: > - write a manpage for f2py Done in f2py CVS. Thanks, Pearu From j_r_fonseca at yahoo.co.uk Sun Feb 15 14:01:48 2004 From: j_r_fonseca at yahoo.co.uk (=?iso-8859-1?Q?Jos=E9?= Fonseca) Date: Sun, 15 Feb 2004 19:01:48 +0000 (UTC) Subject: [SciPy-dev] Re: How to avoid arch specific compiler flags in scipy_distutils? References: Message-ID: Pearu, On Thu, 12 Feb 2004 14:13:29 -0600 (CST), Pearu Peterson wrote: [...] > Btw, the build_src branch is now in HEAD, so > > rm -rf scipy_distutils && cvs update -Pd > > is in order for whoever used build_src branch. > >> If you don't mind commiting this patch below fixing the python binary >> paths, that would save me the trouble of patching-up afterwards: > > Done. > >> So, besides this, the remaining steps to get scipy in debian proper are: >> - write a manpage for f2py > > Done in f2py CVS. Thanks for your tremendous help! The new packages in my repository no longer get any complaint from lintian. I'll now annouce them in the users list just to get some feedback before bugging a mentor. Regards, Jose Fonseca From cjw at sympatico.ca Tue Feb 10 15:56:45 2004 From: cjw at sympatico.ca (Colin J. Williams) Date: Tue, 10 Feb 2004 15:56:45 -0500 Subject: [SciPy-dev] Re: [SciPy-user] "Building Scipy on Windows" notes available In-Reply-To: References: Message-ID: <4029458D.3070801@sympatico.ca> I have tried to resign from this list a number of times, most recently at 09:39 today - see the confirmation below. Could someone please disconnect me? Thanks. Colin W. Mailing list removal confirmation notice for mailing list SciPy-user We have received a request for the removal of your email address, "cjw at sympatico.ca" from the scipy-user at scipy.net mailing list. To confirm that you want to be removed from this mailing list, simply reply to this message, keeping the Subject: header intact. Or visit this web page: http://www.scipy.net/mailman/confirm/scipy-user/3b389cfab24dc30b1da322159fcfb5d741e2c675 Or include the following line -- and only the following line -- in a message to scipy-user-request at scipy.net: confirm 3b389cfab24dc30b1da322159fcfb5d741e2c675 Note that simply sending a `reply' to this message should work from most mail readers, since that usually leaves the Subject: line in the right form (additional "Re:" text in the Subject: is okay). If you do not wish to be removed from this list, please simply disregard this message. If you think you are being maliciously removed from the list, or have any other questions, send them to scipy-user-owner at scipy.net. Pearu Peterson wrote: >Hi all, > >Detailed "from scratch" notes about "Building Scipy on Windows" are >available at > > http://cens.ioc.ee/~pearu/scipy/BUILD_WIN32.html > >It also contains a section on building Win32 port of Atlas libraries >that seems to be a major show-stopper for Windows people, and indeed, I found >it a rather sensitive subject too. Hopefully these notes will help >Windows people to overcome the threshold of building Scipy themself and >may enjoy most recent Scipy features from CVS. > >Best regards, > Pearu > >_______________________________________________ >SciPy-user mailing list >SciPy-user at scipy.net >http://www.scipy.net/mailman/listinfo/scipy-user > > > From val at vtek.com Wed Feb 18 22:23:10 2004 From: val at vtek.com (val) Date: Wed, 18 Feb 2004 22:23:10 -0500 Subject: [SciPy-dev] Re: [SciPy-user] "Building Scipy on Windows" notes available References: <4029458D.3070801@sympatico.ca> Message-ID: <006401c3f697$b391d780$6400a8c0@vt1000> Dear friends, I installed scipy and gist (Windows XP Pro using Windows installers for Python2.3). With scipy i can't run simple methods - both plt and gplt; all imports are Ok: import gui_thread from scipy import gplt (or plt) when it comes to plt.plot(...), it crashes With gist also the imports are Ok from gist import * import gistdemolow when i run gistdemolow.run() i have a message: gist.error: failed to create drawing -- Gist work.gs style sheet missing The file work,gs IS on the path, though. Any suggestions, what i'm doing wrong? Val From nwagner at mecha.uni-stuttgart.de Fri Feb 20 08:13:25 2004 From: nwagner at mecha.uni-stuttgart.de (Nils Wagner) Date: Fri, 20 Feb 2004 14:13:25 +0100 Subject: [SciPy-dev] Urgent: Bug in linalg.lu_factor linalg.lu_solve Message-ID: <403607F5.C043379@mecha.uni-stuttgart.de> Hi all, I have observed a very strange behaviour within linalg.lu_factor / linalg.lu_solve. Any idea or suggestion ? Nils from scipy import * def F(A,l): tmp=zeros((n,n),Complex) tmp[:n,:n] = A+l*identity(n)+exp(-l)*identity(n) return tmp def Fs(l): tmp=zeros((n,n),Complex) tmp[:n,:n] = identity(n)-l*exp(-l)*identity(n) return tmp def T(n): tmp=zeros((n,n),Complex) for i in arange(0,n): tmp[i,i] = -2.0 if i < n-1: tmp[i+1,i] = 1.0 tmp[i,i+1] = 1.0 return tmp n = 4 A = T(n) gamma = 2.0+0j rho = 2.0 ns = 180 #for i in arange(0,ns): for i in arange(0,2): l = gamma+rho*exp(2.*pi*i*1j/ns) D1 = F(A,l) Ds = Fs(l) Dinv = linalg.inv(D1) lu, piv = linalg.lu_factor(D1,overwrite_a=0) tr = 0.0 for k in arange(0,n): rhs = Ds[:,k] g1 = linalg.lu_solve((lu,piv),rhs,trans=0,overwrite_b=0) tr = tr + g1[k] # # tr and trace(dot(Dinv,Ds)) should be the same !!!!! # print tr, trace(dot(Dinv,Ds))