[Python-Dev] GC and Vladimir's obmalloc

[Michael Hudson]

Guido van Rossum <guido@digicool.com> writes:

> So what about the optional memory profiler, on Jeremy's plate?
> 
>     http://sourceforge.net/tracker/index.php?func=detail&aid=401229&group_id=5470&atid=305470
> 
> I'm sure Jeremy would also love it if someone else took care of this
> -- he's busy with the future_statement implementation.

In a way, I think this is less important.  IMO, only people with a
fair amount of wizadry are going to want to use this, and telling them
to go and get the patch and apply it isn't too much of a stretch
(though it would help if it applied cleanly...).

OTOH, obmalloc can improve performance (esp. if Neil can do his cool
GC optimizations with it), and so it becomes more important to get it
into 2.1 (as a prelude to turning it on by default in 2.2, right?).

Just my opinion,
M.

-- 
  This is the fixed point problem again; since all some implementors
  do is implement the compiler and libraries for compiler writing, the
  language becomes good at writing compilers and not much else!
                                 -- Brian Rogoff, comp.lang.functional