[Pysparse-developers] Python 2.5 and memory management

[Adam C P. IV <haz...@de...>]

Greetings,

First, let me introduce myself: I'm the maintainer of the Debian package
of pysparse.  The package takes a somewhat different approach from
upstream: instead of building the superlu, umfpack and amd sources in
the pysparse package, it links to existing Debian packages for those.

This is an "FYI" on Debian bug 468991, viewable at
http://bugs.debian.org/468991 .  The bug submitter asserts that the
memory management model of python 2.5 has changed, such that objects
created using PyObject_NEW should use PyObject_Del in their destructors,
not PyMem_DEL.

According to Thomas Viehmann, this will not cause a segfault in
pysparse, but should be cleaned up eventually.  I figured you should be
aware of this as a maintenance "To-Do" item.

I'll leave this bug open until pysparse changes.

Thanks,
-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/