Hello Brian, Am So., 29. Sept. 2019 um 22:59 Uhr schrieb Brian Theado < brian.the...@gmail.com>:
> Edward can speak to the built-in leo traces, but there are also other > options. > > I mentioned in the thread at > https://groups.google.com/forum/#!topic/leo-editor/r6ktpQNWySk, about > using the python trace module for debugging python applications, but I no > longer recommend using it because it is too difficult to filter out noise. > Since then I've discovered https://github.com/ionelmc/python-hunter and > it is excellent. You can filter exactly which modules do and don't get > traced and the colorized output looks nice. > > Depending on what pattern of modules you pick to trace you will still get > a firehose of information. You can either fine-tune your python-hunter > queries more or just save the trace output to a file which you can search > through. > > ... > > Not sure this is really what you are after, but I thought I'd share in > case in helps. > It's not exactly what I'm after, but your description - as well as - the README of python-hunter makes it clear, that this is an option I'll investigate further. Thanks a lot for sharing! With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAAeSrG%2B7i7z8tg_X%3DCZJDRxrZ%3DCF65VvDDMk_QZFgK4q4%2B0VYA%40mail.gmail.com.
