Skip to content

Commit 549cac8

Browse files
committed
use class tags
1 parent 51a9058 commit 549cac8

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

lectures/debugging.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -122,14 +122,14 @@ plot_log() # Call the function, generate plot
122122
But this time we type in the following cell block
123123

124124
```{code-block} ipython
125-
:no-execute:
125+
:class: no-execute
126126
%debug
127127
```
128128

129129
You should be dropped into a new prompt that looks something like this
130130

131131
```{code-block} ipython
132-
:no-execute:
132+
:class: no-execute
133133
ipdb>
134134
```
135135

@@ -141,7 +141,7 @@ For example, here we simply type the name `ax` to see what's happening with
141141
this object:
142142

143143
```{code-block} ipython
144-
:no-execute:
144+
:class: no-execute
145145
ipdb> ax
146146
array([<matplotlib.axes.AxesSubplot object at 0x290f5d0>,
147147
<matplotlib.axes.AxesSubplot object at 0x2930810>], dtype=object)
@@ -154,7 +154,7 @@ To find out what else you can do from inside `ipdb` (or `pdb`), use the
154154
online help
155155

156156
```{code-block} ipython
157-
:no-execute:
157+
:class: no-execute
158158
ipdb> h
159159
160160
Documented commands (type help <topic>):
@@ -208,7 +208,7 @@ To investigate, it would be helpful if we could inspect variables like `x` durin
208208
To this end, we add a "break point" by inserting `breakpoint()` inside the function code block
209209

210210
```{code-block} python3
211-
:no-execute:
211+
:class: no-execute
212212
def plot_log():
213213
breakpoint()
214214
fig, ax = plt.subplots()
@@ -222,7 +222,7 @@ plot_log()
222222
Now let's run the script, and investigate via the debugger
223223

224224
```{code-block} ipython
225-
:no-execute:
225+
:class: no-execute
226226
> <ipython-input-6-a188074383b7>(6)plot_log()
227227
-> fig, ax = plt.subplots()
228228
(Pdb) n

0 commit comments

Comments
 (0)