python-cdb-0.34 addresses this issue: http://pilcrow.madison.wi.us
/python-cdb/python-cdb-0.34.tar.gz
--
Segfaults with Python 2.5
https://bugs.launchpad.net/bugs/222146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Set to Triaged based on the last comment
** Changed in: python-cdb (Ubuntu)
Status: Incomplete = Triaged
--
Segfaults with Python 2.5
https://bugs.launchpad.net/bugs/222146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Shane,
thanks for reporting this bug and for working on a fix.
However I'm not sure if this bug is still reproducible with the latest version
of python-cdb, can you please try to reproduce this bug with an updated
installation of your ubuntu system.
If this bug is still reproducible, can you
Markus,
I no longer have access to the system where it was failing, so I can not
reproduce it anymore.
The issue remains that the package is using the wrong API and the
upstream maintainer seems to be MIA. Since about Python 2.0,
PyObject_Del, not PyMem_Del, is the correct API for most users of
Note that this is very similar to bug #115655. Applying the patch might
also solve bug #157251.
--
Segfaults with Python 2.5
https://bugs.launchpad.net/bugs/222146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Simple patch against python-cdb
http://launchpadlibrarian.net/13908278/python-cdb-0.32-python-2.5-compat.patch
--
Segfaults with Python 2.5
https://bugs.launchpad.net/bugs/222146
You received this bug notification because you are a member of Ubuntu
Bugs, which is
