[SciPy-dev] Compiling pysparse from the sandbox
Thu Apr 19 12:24:13 CDT 2007
On Thu, 19 Apr 2007 16:46:37 +0100
"Ed Schofield" <firstname.lastname@example.org> wrote:
>> On 4/18/07, Daniel Wheeler <email@example.com>
>> On Apr 18, 2007, at 6:53 PM, Bill Baxter wrote:
>>> I think the name changed from CONTIGUOUS to
>>> NPY_C_CONTIGUOUS if you want to be a little more
>>>explicit). Or try
>>> including numpy/noprefix.h instead of whatever it is
>>> That's apparently a compatibility header.
>>> So is this pysparse in the sandbox the same pysparse as
>> Probably not. Pysparse at sourceforge is being
>>maintained and is at release
>> 1.0. It's been updated
>> to use numpy with the numpy/noprefix.h method mentioned
>>above. Use cvs
>> rather than 1.0 as 1.0
>> doesn't see the numpy header files.
> That's interesting to hear; I haven't been following
> development for a while. Around the time of the Numeric
>-> SciPy core
> transition, I took a snapshot of PySparse, patched it to
> NumPy and added it to the sandbox, with the idea of
>using it as a
> basis for improvements to (or even a re-write of) the
> module. But we decided to keep the existing scipy.sparse
> and when I came to add the new list-based lil_matrix
>type, it turned
> out to be easier to design it from scratch rather than
> ll_mat.c code to Python.
> So I see no reason to keep the pysparse snapshot in the
> longer. I've actually been meaning for a while to
>propose that we
> delete it from the tree...
> -- Ed
> Scipy-dev mailing list
Just now I have installed the latest pysparse via cvs, but
I need some advice to improve my local setup.py.
I have already installed BLAS/LAPACK,ATLAS and
UMFPACK from source.
So, who can send me a customized setup.py for pysparse ?
More information about the Scipy-dev