Sumner Hayes wrote:
> Python 2.5 has tightened up the way it handles memory
> allocation, and there's a mis-match in the way that
> if_python.c handles memory allocation which worked
> with earlier Python versions but causes vim to
> seg-fault with 2.5. Essentially, PyMem_DEL shouldn't
> be pair
Hi all,
Python 2.5 has tightened up the way it handles memory
allocation, and there's a mis-match in the way that
if_python.c handles memory allocation which worked
with earlier Python versions but causes vim to
seg-fault with 2.5. Essentially, PyMem_DEL shouldn't
be paired with PyObject allocati
