Gabriel Genellina wrote:
> Python got in 2.3 a heapq module in its standard library; I think it is what
> Ah! then I bet:
> - There is some C code involved.
> - It carelessly mixes PyMem_Malloc with PyObject_Free or similar as
> described in
> http://docs.python.org/whatsnew/ports.html
>
> So do y
On 20/01/2007 11.29, Martin v. Löwis wrote:
>> I haven't got a clue how to investigate this, but I would be willing to
>> help if someone has any ideas.
>
> There are a number of problems in this code; the most significant one is
> the incorrect usage of memory management API. In pqueue_dealloc,
Berteun Damman schrieb:
> I haven't got a clue how to investigate this, but I would be willing to
> help if someone has any ideas.
There are a number of problems in this code; the most significant one is
the incorrect usage of memory management API. In pqueue_dealloc, the
call PyMem_DEL(pqp) shoul
"Berteun Damman" <[EMAIL PROTECTED]> escribió en el mensaje
news:[EMAIL PROTECTED]
> Recently I was looking for a Priority Queue module, and I've found
> Pqueue by Andrew Snare [1].
That appears to be rather ancient, from 1999. Is it a pure Python
implementation or has some C code too?
Python g
Hello,
Recently I was looking for a Priority Queue module, and I've found
Pqueue by Andrew Snare [1]. When I use it with Python 2.4 everything
works okay, at least on the two system I've tested it on (Debian based
AMD 64) and OS PPC.
However, when I use it with Python 2.5 - again on the same mach
