> > That is not expected. _make_method_ stores a copy of the method in
> > self._builtMethods_ (line 309). A further __getattr__ for
> that name should
> > locate it. You may have found a 'bug' (or maybe it should
> be called an
> > un-optimization) when the default method name is used
> though
> That is not expected. _make_method_ stores a copy of the method in
> self._builtMethods_ (line 309). A further __getattr__ for that name should
> locate it. You may have found a 'bug' (or maybe it should be called an
> un-optimization) when the default method name is used though - what is the
> I have investigated this further and found that python appears to
> compile the Value call for each loop iteration (dynamic.py, row 300).
> The compiled python objects are somehow kept during the lifetime of
> the script. Is this correct?
That is not expected. _make_method_ stores a copy of the
> I have set breakpoint on malloc and free in the runtime library and have
> observed that Python calls these functions frequently, which I suspect is
> part of the problem.
I have investigated this further and found that python appears to
compile the Value call for each loop iteration (dynamic.py
