![]() Note that you don’t need to use breakpoints – if you start the debugger without breakpoints, Thonny stops before the first statement, just like it used to. This gives you the margin, where you can add or remove breakpoints with double-clicks. For using them, you need to switch on line numbers (Tools → Options → Editor). Last, but not least, Thonny finally supports breakpoints. Note that both styles can be used with both debugging modes. In “Tools → Options → Debugger” you can switch to more traditional style with a separate view for presenting and switching call frames. ![]() Therefore in 3.0 one can choose between two different styles for presenting call stack. This gives good intuition about the concept, but it may become cumbersome to use. We expect that most students start with the nicer debuger and move on to the faster one when their programs grow bigger.īy default the new debugging mode still uses stacked windows for presenting the call stack. The new mode is not as intuitive but much more efficient. Beside the original AST-based debug mode – the “nicer” one (Ctrl+F5), there is new, traditional line-based mode – the “faster” one (Shift+F5). Although the performance has been greatly improved in 3.0 beta, larger programs would still benefit from a more efficient solution. The original debugger has been very useful for explaining the meaning of Python constructs, but its memory and time overhead became noticeable when making bigger steps in some programs (especially after the introduction of stepping back in time). ![]() Thanks to the support from Raspberry Pi Foundation, Thonny now has several new debugger-related features.
0 Comments
Leave a Reply. |