From ab79934e705f5d4f458406b8cb0207422e260f28 Mon Sep 17 00:00:00 2001 From: Robert Chisholm Date: Fri, 22 Mar 2024 16:04:19 +0000 Subject: [PATCH] Fixup, suggested changes included some typographic issues. --- episodes/profiling-functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/episodes/profiling-functions.md b/episodes/profiling-functions.md index 6677d19..367f1a1 100644 --- a/episodes/profiling-functions.md +++ b/episodes/profiling-functions.md @@ -337,7 +337,7 @@ If you followed along inside a notebook it might look like this: ![The worked example inside a notebook.](episodes/fig/snakeviz-worked-example-notebook.png){alt="A Jupyter notebook showing the worked example profiled with snakeviz." width=80%} -Because notebooks operate by creating temporary Python files, the filename (shown `1378276351.py` above) and line numbers are not too useful should still be helpful. The function names follow the temporary file name in parentheses, e.g. `1378276351.py:3(a_1)`, `1378276351.py:9(b_1)` and so forth. +Because notebooks operate by creating temporary Python files, the filename (shown `1378276351.py` above) and line numbers displayed are not too useful. However, the function names match those defined in the code and follow the temporary file name in parentheses, e.g. `1378276351.py:3(a_1)`, `1378276351.py:9(b_1)` refer to the functions `a_1()` and `b_1()` respectively. ::::::::::::::::::::::::::::::::::::: callout