Namespace leaks are tracked at the wrong scope

The namespace leak tracking system stores a dictionary on the code
reloader, that uses as a key the attribute name and as the value, a tuple
of script path and script version.  There is no way of knowing in what
namespace the attribute by that name was leaked.

The leaks should be tracked on a per namespace basis.  Either
namespace.__name__ can be used as a key, or some clean way can be found of
storing it on/in the namespace.  In fact, that might be the best solution.

Original issue reported on code.google.com by richard.m.tew@gmail.com on 13 Feb 2010 at 7:43

johnbickmore / livecoding

Namespace leaks are tracked at the wrong scope #16