Deleting sandbox.pysparse
Hi everyone, The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it? -- Ed
Ed Schofield wrote:
Hi everyone,
The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it?
There were some messages on this list today from people using Pysparse. Perhaps the maintainer of Pysparse (Daniel Wheeler I believe) should be contacted to see if he would agree to maintain Pysparse as part of SciPy. I think it would be a great feature. Dominique
On 6/29/07, Dominique Orban <dominique.orban@gmail.com> wrote:
Ed Schofield wrote:
Hi everyone,
The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it?
There were some messages on this list today from people using Pysparse. Perhaps the maintainer of Pysparse (Daniel Wheeler I believe) should be contacted to see if he would agree to maintain Pysparse as part of SciPy. I think it would be a great feature.
I don't know whether we'd want to merge Pysparse into the SciPy tree. I think the code would be difficult to integrate with the existing scipy.sparse package (partly because they use different languages). And if they lived separate lives in the scipy namespace we wouldn't really have gained anything. In any case we'd want to start by removing the obsolete cruft in the sandbox. ;) -- Ed
On Fri, 29 Jun 2007, Dominique Orban apparently wrote:
Pysparse. Perhaps the maintainer of Pysparse (Daniel Wheeler I believe) should be contacted to see if he would agree to maintain Pysparse as part of SciPy. I think it would be a great feature.
I am not currently using Pysparse. But looking forward, that would be great! Cheers, Alan Isaac
On Jun 29, 2007, at 4:24 PM, Dominique Orban wrote:
Ed Schofield wrote:
Hi everyone,
The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it?
There were some messages on this list today from people using Pysparse. Perhaps the maintainer of Pysparse (Daniel Wheeler I believe) should be contacted to see if he would agree to maintain Pysparse as part of SciPy. I think it would be a great feature.
As far as my project is concerned, I would prefer that pysparse remains at sourceforge for the time being. Our python code (fipy) relies heavily on pysparse and I believe that it is easier for users to install pysparse as a small package rather than making scipy a requirement. Having said that, I guess it wouldn't be too difficult to move pysparse into the scipy repository and still build separate snapshots of pysparse and upload then to sourceforge for users who only want pysparse. However, I believe that having two incompatible sparse matrix and linalg modules within scipy just causes confusion. Ripping pysparse code may be useful to help improve scipy's solver and linalg modules, but merely maintaining it in the sandbox separate from the scipy solvers (as it has been) just adds to the confusion. Cheers -- Daniel Wheeler
On Mon, 2 Jul 2007, Daniel Wheeler apparently wrote:
As far as my project is concerned, I would prefer that pysparse remains at sourceforge for the time being. Our python code (fipy) relies heavily on pysparse and I believe that it is easier for users to install pysparse as a small package rather than making scipy a requirement.
Having said that, I guess it wouldn't be too difficult to move pysparse into the scipy repository and still build separate snapshots of pysparse and upload then to sourceforge for users who only want pysparse.
If it were a SciKit, users could simply retrieve the package from SVN and install it as usual, without I think adding any SciPy dependency. (I am not trying to say this is the right way to go.) Cheers, Alan Isaac
On 6/29/07, Ed Schofield <edschofield@gmail.com> wrote:
The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it?
I think it is a good idea to remove the old cruft, so you have my vote to remove pysparse. I haven't been using it, though, so I don't know how much my vote should count. Should people currently using the pysparse code from the sandbox just start using the code from the sourceforge page? -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
On 6/29/07, Jarrod Millman <millman@berkeley.edu> wrote:
On 6/29/07, Ed Schofield <edschofield@gmail.com> wrote:
The pysparse snapshot in the sandbox is old and unmaintained, and I'd like to remove it from the SVN tree. Is anyone using it?
I think it is a good idea to remove the old cruft, so you have my vote to remove pysparse. I haven't been using it, though, so I don't know how much my vote should count.
Should people currently using the pysparse code from the sandbox just start using the code from the sourceforge page?
Yes -- if such creatures exist... -- Ed
participants (5)
-
Alan G Isaac -
Daniel Wheeler -
Dominique Orban -
Ed Schofield -
Jarrod Millman