GitHub

Original file line numberDiff line numberDiff line change

@@ -121,13 +121,15 @@ plot_log() # Call the function, generate plot

121121
122122

But this time we type in the following cell block

123123
124-

```ipython

124+

```{code-block} ipython

125+

:class: no-execute

125126

%debug

126127

```

127128
128129

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

129130
130-

```ipython

131+

```{code-block} ipython

132+

:class: no-execute

131133

ipdb>

132134

```

133135

@@ -138,7 +140,8 @@ Now we can investigate the value of our variables at this point in the program,

138140

For example, here we simply type the name `ax` to see what's happening with

139141

this object:

140142
141-

```ipython

143+

```{code-block} ipython

144+

:class: no-execute

142145

ipdb> ax

143146

array([<matplotlib.axes.AxesSubplot object at 0x290f5d0>,

144147

<matplotlib.axes.AxesSubplot object at 0x2930810>], dtype=object)

@@ -150,7 +153,8 @@ problem.

150153

To find out what else you can do from inside `ipdb` (or `pdb`), use the

151154

online help

152155
153-

```ipython

156+

```{code-block} ipython

157+

:class: no-execute

154158

ipdb> h

155159
156160

Documented commands (type help <topic>):

@@ -203,7 +207,8 @@ To investigate, it would be helpful if we could inspect variables like `x` durin

203207
204208

To this end, we add a "break point" by inserting `breakpoint()` inside the function code block

205209
206-

```python3

210+

```{code-block} python3

211+

:class: no-execute

207212

def plot_log():

208213

breakpoint()

209214

fig, ax = plt.subplots()

@@ -216,7 +221,8 @@ plot_log()

216221
217222

Now let's run the script, and investigate via the debugger

218223
219-

```ipython

224+

```{code-block} ipython

225+

:class: no-execute

220226

> <ipython-input-6-a188074383b7>(6)plot_log()

221227

-> fig, ax = plt.subplots()

222228

(Pdb) n

Read the original on github.com ↗