GC In Python: YAS (Yet Another Summary)

[Christian Tismer]

Vladimir Marangozov wrote:
> 
> A not very modest plug
> 
> Tim Peters wrote:
> >
> > [Andrew Dalke, worries about Boehm collection vs Fortran]
> > ...
> > Despite all that, it would probably work fine for you.  I think it's a dead
> > issue here regardless, though, because Guido isn't going to tell anyone they
> > have to use a particular routine for memory allocation.  Python could use
> > its own malloc for its own objects (& Vladimir Marangozov has written a very
> > nice PyMalloc, available from his Starship page), but
> 
> Thanks for the compliment, but ...
> 
> > that breaks down as soon as any extension has its own view of how to get memory.
> 
> I can't let you say this (heh, it's too late ;-) because you seem to
> overlook one of the nicest features of pymalloc. If the extension module
> works in current Python + libc malloc, it will work with Python +
> pymalloc
> because of the dynamic block management. IOW, if one recompiles the core
> with pymalloc instead of the usual libc malloc, everything should work
> as before, even *without* recompiling any extension or 3rd party
> modules.

It is a great concept to catch just one aspect
(as in you case, small blocks) and leave the rest as it was.

> The concept is simple, but useful. I told you that pymalloc is tricky
> ;-)

Welcome in the club. You know what me thinks of tricky code ;-)

ciao - chris

-- 
Christian Tismer             :^)   <mailto:tismer at appliedbiometrics.com>
Applied Biometrics GmbH      :     Have a break! Take a ride on Python's
Kaiserin-Augusta-Allee 101   :    *Starship* http://starship.python.net
10553 Berlin                 :     PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint       E182 71C7 1A9D 66E9 9D15  D3CC D4D7 93E2 1FAE F6DF
    About to publish true continuations which are very tricky. Pah!