bug lies in (presently) unused code path

2008-03-06 Thread Thomas Viehmann
user [EMAIL PROTECTED] usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/e

bug lies in (presently) unused code path

2008-03-05 Thread Thomas Viehmann
user [EMAIL PROTECTED] usertag 468977 -goal-python2.5 retitle 468977 Python API memory handling bug in unused code path found 468977 0.90.1-3.1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in matplotlib-0.90.1/src/_subprocess.c) is not actually compiled and th

bug lies in (presently) unused code path

2008-03-05 Thread Thomas Viehmann
user [EMAIL PROTECTED] usertag 469001 -goal-python2.5 severity 469001 normal retitle 469001 buggy Python API memory handling in unused source code found 469001 0.6.0-8 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in python-scipy-0.6.0/scipy/sandbox/netcdf/_ne

bug lies in (presently) unused code path

2008-03-04 Thread Thomas Viehmann
user [EMAIL PROTECTED] usertag 468965 -goal-python2.5 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in ecasound2.2-2.4.6.1/pyecasound/pyecasound.c) is not actually compiled and the results shipped. As such, while a fix still seems to be worthwile it does not

bug lies in (presently) unused code path

2008-03-04 Thread Thomas Viehmann
user [EMAIL PROTECTED] usertag 468970 -goal-python2.5 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in egenix-mx-base-3.0.0/mx/Tools/mxTools/xmap.c) is not actually compiled and the results shipped. As such, while a fix might still be worthwile it does n