Issue 16 in livecoding: Namespace leaks are tracked at the wrong scope
livec...@googlecode.com
Owner: richard.m.tew
Labels: Type-Defect Priority-High
New issue 16 by richard.m.tew: Namespace leaks are tracked at the wrong
scope
http://code.google.com/p/livecoding/issues/detail?id=16
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.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
livec...@googlecode.com
Status: Verified
Comment #1 on issue 16 by richard.m.tew: Namespace leaks are tracked at the
wrong scope
http://code.google.com/p/livecoding/issues/detail?id=16
http://code.google.com/p/livecoding/source/detail?r=140