Re: [Pysparse-users] memory leak

[Daniel W. <dan...@gm...>]

One more thing when I build pysparse I noticed that I'm getting a "-g"
compiler argument? For example,

gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -DUSE_VENDOR_BLAS=1 -DNUMPY=1 -Isuperlu
-IInclude -I/users/wd15/usr/i686/5.0/lib/python2.5/site-packages/numpy/core/include
-I/usr/include/python2.5 -c superlu/util.c -o
build/temp.linux-i686-2.5/superlu/util.o

How do I get rid of that? I'm using the setup.py from 1_1_x.

2010/6/4 Dominique Orban <dom...@gm...>:
> 2010/6/4 Łukasz Pankowski <lu...@o2...>:
>> Daniel Wheeler <dan...@gm...> writes:
>>
>>> Can I do a 1.1.1 release? Any objections? Find() method  is quite
>>> important for fipy right now.
>>
>> Could you apply my old patch (2009-12-09) before the release:
>>
>> ll_mat: fix raising IndexError for invalid indices - ID: 2911619
>> http://sourceforge.net/tracker/?func=detail&aid=2911619&group_id=101403&atid=629638
>
> Lukasz,
>
> Very sorry we missed this patch somehow. I fixed the new-setup branch.
>
> Daniel, should we be thinking about making new-setup the default in
> Pysparse? That is the one using the "standard" distutils layout and is
> the one in the Python Package Index. Have you tried it with FiPy?
>
> --
> Dominique
>



-- 
Daniel Wheeler