bug lies in (presently) unused code path

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

pysparse: no PyObject_New / PyMem_Del confusion, removing goal-python2.5

user [EMAIL PROTECTED] usertag 468991 -goal-python2.5 severity 468991 normal retitle 468991 Python API memory handling could use cleanup found 468991 1.0.1-4 thanks Hi, as detailed in my mail to the bug report[1], the memory handling with PyObject_* vs. PyMem_* is done correctly in pysparse,

buggy Python API memory handling in (uncompiled) example C code

user [EMAIL PROTECTED] usertag 468987 -goal-python2.5 severity 468987 normal retitle 468987 buggy Python API memory handling in example C code found 468987 0.beta1-3.4 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in pygdchart2-0.beta1/doc/images/gdmodule-0.42/

bug lies in (presently) unused code path

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