Master debugging

[Benjamin-Loison]

To avoid writing temporary instructions in code just for debugging.

Notably debug with just pausing and resuming execution which would not be resumable easily by just executing part of the script.

Related to #33.

+8

[Benjamin-Loison]

Notably to know what line we are currently executing which may be unclear when execute whole script and there is no clear debugging prints.

[Benjamin-Loison]

Example Python script taking time:

```python import time SECONDS_TO_SLEEP = 3 iteration = 0 def printIteration(toPrint): print(f'Iteration {iteration}: {toPrint}') while True: printIteration(f'Sleeping {SECONDS_TO_SLEEP} seconds...') time.sleep(SECONDS_TO_SLEEP) printIteration(f'Finished sleeping {SECONDS_TO_SLEEP} seconds!') print() iteration += 1 ```

[Benjamin-Loison]

Related to #51, Getting started with Pyzo does not seem to help.

[Benjamin-Loison]

Both Shell and Shells have some buttons but unclear to make them available and use.

Maybe have to use Interrupt the current running code (does not work for extension code):

Output:

``` >>> (executing cell "" (line 1 of "")) Iteration 0: Sleeping 3 seconds... Iteration 0: Finished sleeping 3 seconds! Iteration 1: Sleeping 3 seconds... Iteration 1: Finished sleeping 3 seconds! Iteration 2: Sleeping 3 seconds... Traceback (most recent call last): File "", line 12, in time.sleep(SECONDS_TO_SLEEP) KeyboardInterrupt ```

the goal is then to resume.

Another time got:

Stop debugging results in:

Even with setting a yellow circle I still face the same behaviors.

[Benjamin-Loison]

Shell > Postmortem: debug from last traceback does not seem to do anything when the script is running.

[Benjamin-Loison]

Debugging next/step/continue. Post-mortem debugging.

Source: https://pyzo.org/features.html

Interactivity (ways to run code) does not help.

Tools does not have a specific tab but Workspace is interesting by listing all variables etc. Alternatively whos, source: https://pyzo.org/screenshots.html.

https://pyzo.org/interactive_vs_script.html does not help.

[Benjamin-Loison]

However, in my case I do not know where to put a breakpoint.

[Benjamin-Loison]

It does seem however that step-into doesn't (yet?) work well (i.e. stopping in one line and then stepping into another function) unless you set up another break-point.

Source: the Stack Overflow answer 38943360 (Aug 14, 2016 at 14:49)

[Benjamin-Loison]

https://pyzo.narkive.com/VbtSv80m/how-to-use-the-new-debug-mode-in is about setting breakpoints, so not interesting in our case.

[Benjamin-Loison]

Pyzo debugger on DuckDuckGo and Google first page of results do not seem very interesting.

Should watch YouTube: tM9YUWVQ26A.

Maybe can just set a breakpoint at the start and then run but I do not see how to resume from interruption:


Is it even possible without Pyzo?

[Benjamin-Loison]

Related to Benjamin_Loison/codeblocks/issues/10.

[Benjamin-Loison]

Highlighting line being executed would be nice and would maybe avoid Benjamin-Loison/cpython/issues/40.

[Benjamin-Loison]

Related to Benjamin-Loison/cpython/issues/22.

[Benjamin-Loison]

Note environ PYZO_PROCESS_EVENTS_WHILE_DEBUGGING=1.