You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/TRACEBACKS.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,13 +207,13 @@ print(sum)
207
207
208
208
Running this code will give you a prompt where you can type in commands.
209
209
Write `help` to get a list of commands.
210
-
The most common onces are `step` which steps into a function called at that line.
211
-
`next`which steps over a function call and move to the next line. `where` which tells you which line you are on.
212
-
Some other usefull commands are `whatis <variable>` which tells you the type of a variable and `print(<variable>)` which prints the value of a variable.
210
+
The most common ones are `step` which steps into a function called at that line.
211
+
`next` steps over a function call and move to the next line. `where` tells you which line you are on.
212
+
Some other useful commands are `whatis <variable>` which tells you the type of a variable and `print(<variable>)` which prints the value of a variable.
213
213
You can also just use `<variable>` to print the value of a variable.
214
214
Another command is `jump <line number>` which jumps to a specific line number.
215
215
216
-
Here are an example on how to use the debugger based on the code earlier:
216
+
Here is an example of how to use the debugger based on the code earlier:
217
217
218
218
```python
219
219
>>> python pdb.py
@@ -238,14 +238,14 @@ Here are an example on how to use the debugger based on the code earlier:
238
238
... (Pdb)
239
239
```
240
240
241
-
Breakpoints is setup by `break <filename>:<line number> <condition>` where condition is an optional condition that has to be true for the breakpoint to be hit.
241
+
Breakpoints are set up by `break <filename>:<line number> <condition>` where the condition is an optional condition that has to be true for the breakpoint to be hit.
242
242
You can simply write `break` to get a list of the breakpoints you have set.
243
243
To disable a breakpoint you can write `disable <breakpoint number>`.
244
244
To enable a breakpoint you can write `enable <breakpoint number>`.
245
245
To delete a breakpoint you can write `clear <breakpoint number>`.
246
246
To continue execution you can write `continue` or `c`. To exit the debugger you can write `quit` or `q`.
247
247
248
-
Here are an example on how to use the debugger based on the code earlier:
248
+
Here is an example of how to use the debugger based on the code earlier:
0 commit comments