Edward, On Thu, Nov 29, 2012 at 7:41 AM, Edward K. Ream <[email protected]> wrote:
> Recent revs contain work on a nifty new tracing tool: the SherlockTracer > class in leoGlobals.py. This is a stand-alone class: it is not a subclass > of pdb.Pdb, and it requires no imports (it does it's own imports) > [...] Being able to zero in on the code of interest can be a big help in studying > other people's code. This is a non-invasive method: no tracing code needs > to be inserted anywhere. > [...] How does this compare to the python trace module ( http://docs.python.org/2/library/trace.html)? It looks to me like sherlock filters are more powerful as trace supports only 'ignoremods' and 'ignoredirs'. Maybe there are other differences as well. Last year I wrote some code which inserts call tree output from the trace module into leo headlines. If it sees the same function in multiple places in the call tree, then it uses clones to avoid duplication. Having the calltree in headlines makes it convenient to only expand those nodes which are of interest. I posted the code here: https://groups.google.com/d/topic/leo-editor/yLRMXw4Yvv4/discussion (as mentioned there, my code was inspired by Ville's code in scripts.leo). Brian -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
