[SciPy-dev] Introductions, sparse matrix support

Ed Schofield schofield at ftw.at
Mon Oct 17 05:18:10 CDT 2005

Jonathan Guyer wrote:

>On Oct 13, 2005, at 1:53 PM, Travis Oliphant wrote:
>>I'd happily welcome those extension types, but let's see if we can't
>>make them all subclasses of one base-class.   Look at how the scipy
>>sparse Python classes are layed out.  Basically, by defining a tocsc 
>>fromcsc, all of them can be converted to each other and used as 
>>I did put some effort into the structure of scipy.sparse.   I did not
>>put any effort into optimizations, though.
>I think this is important. PySparse is neither very object oriented nor 
>very "Pythonic". I think the API can be done much better [*] (and 
>scipy.sparse may be it; I haven't had time yet to do anything practical 
>with it). I don't mean to denigrate PySparse; we happily use it and 
>Roman has been very open to our suggestions, I just think that we can 
>learn from it and do better.

Okay then, let's use the existing sparse module's structure as a base.

I'd like to ask for clarification about the versions in SVN.  The most
complete version seems to be


but what are the branches numeric_subpackage_branch{,2}/Lib/sparse?  Are
these dead and buried?

More information about the Scipy-dev mailing list