Re: Debugging with Leo: getting started?

On Monday, August 12, 2019 at 6:13:29 AM UTC-5, btheado wrote: As Edward says, adding a call to pdb.set_trace() works. This assumes you > already know where to put the breakpoint. If you don't, then one way is > just start pdb before any code executes and start stepping through the > code. >

Re: Debugging with Leo: getting started?

On Tue, Aug 13, 2019 at 12:41 AM Matt Wilkie wrote: or, doh! use a different join() statement. Sheesh Matt! > > python -c "import sys ; print(';'.join(sys.path)[1:])" > :-) As a general rule, newbies (in whatever area) should cut themselves a huge amount of slack. Edward -- You received this

Re: Debugging with Leo: getting started?

On Monday, 12 August 2019 22:38:43 UTC-7, Matt Wilkie wrote: > > *(I hit [post] by mistake. Some of you may get a partial message before > this full one)* > > I needed to change some things to get working in Windows. For the ignore > list of system directories: reverse the inner and outer

Re: Debugging with Leo: getting started?

*(I hit [post] by mistake. Some of you may get a partial message before this full one)* I needed to change some things to get working in Windows. For the ignore list of system directories: reverse the inner and outer quotes, capture to text file. Edit path to use Win path separator instead of

Re: Debugging with Leo: getting started?

For Windows I needed to change some things: But this has way too much output so it is better to filter out all the > standard python library calls. Do that by running this command to get this > list of directories to ignore: > > python -c 'import sys ; print(":".join(sys.path)[1:])' > > reverse

Re: Debugging with Leo: getting started?

On Mon, Aug 12, 2019 at 10:26 AM Matt Wilkie wrote: > thank you both so much. (((learning hat on...))) > You're welcome. That's the spirit ;-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Debugging with Leo: getting started?

thank you both so much. (((learning hat on...))) -- 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

Re: Debugging with Leo: getting started?

As Edward says, adding a call to pdb.set_trace() works. This assumes you already know where to put the breakpoint. If you don't, then one way is just start pdb before any code executes and start stepping through the code. Usually this is tiresome because you end up stepping through a lot of code

Re: Debugging with Leo: getting started?

On Sun, Aug 11, 2019 at 7:29 PM Matt Wilkie wrote: I figured I'd buckle down and learn how to use a debugger properly like the > Smart Kids Do. > Insert calls to g.pdb(). This will start Python's pdb debugger . You must be running Leo from a console.

Debugging with Leo: getting started?

Hi All, I'm in the middle of trying to understand how a 3rd party python module and utility works (ref ). The complications surpass my fledging debugging approach of liberally sprinkling print() statements everywhere, so I figured I'd buckle down and