Re: [Pysparse-users] memory leak

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

Hi Dominique,

I tried the new-setup-py branch against fipy and everything worked
fine with the following small change:

bunter[wd15]: svn diff
Index: pysparse/__init__.py
===================================================================
--- pysparse/__init__.py        (revision 177)
+++ pysparse/__init__.py        (working copy)
@@ -5,6 +5,7 @@
 # Imports
 from numpy._import_tools import PackageLoader
 from version import version as __version__
+from sparse import spmatrix

 #from sparse import *
 from misc import get_include

The organization seems greatly improved. Thanks for all the hard work.
Is the change above acceptable?

On Fri, Jun 4, 2010 at 11:06 AM, Dominique Orban
<dom...@gm...> wrote:
> On Fri, Jun 4, 2010 at 3:37 PM, Daniel Wheeler
> <dan...@gm...> wrote:
>> 2010/6/4 Dominique Orban <dom...@gm...>:
>>
>>> 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?
>>
>> Net yet. I'll try it with fipy and then you can merge it back into
>> trunk. I'm going to make a release from the version 1_1_x branch
>> anyway (not from trunk) with the minor bug fixes we've been making so
>> this is irrelevant right now. Once you are happy with your merge we
>> can do a version 1.2 release from trunk. Does that sound reasonable?
>
> Sounds good. I'll wait for your comments on using the new-setup branch
> with Fipy. There will be some namespace adjustments required. Of
> course, the namespace can be adjusted too.
>
> --
> Dominique
>



-- 
Daniel Wheeler