Index and value errors in Chapter 3 #21
Comments
|
Thanks for reporting this, this is not your fault. I rebuilt the book recently and I think the book generation is picking up the wrong settings. |
|
It's odd that higher up in the chapter, indexing is being done with In section 3.6, indexing is still Further down the chapter, there are some interactions with workspaces, loading and saving things. Maybe one of those is interfering with |
|
@rodrigogiraoserrao for long chapters, it may be worthwhile doing some defensive coding and resetting the interpreter to known conditions in various points in the chapter with the |
I understand what you mean, but I don't get why you suggest that: the notebooks are written in a linear sequence, and each chapter starts with a clean session. As for this issue, I am still trying to figure out what is happening, because opening the chapter notebook on my computer and re-executing the whole notebook doesn't result in any issues whatsoever. |
The INDEX ERRORs that were happening arose because the MyPreciousWs that was being loaded in the section about workspaces had been saved, somehow, with ⎕IO ← 0, which meant that loading it was throwing off the remainder of the calculations. Supposedly, this issue would never really arise because the workspace was first being saved from within the notebook, and only then loaded. However, because the workspace already existed in the �ook folder, the first attempt to )save it was failing: the current workspace was the clear workspace and we were trying to save on top of a named workspace. To fix this, I had to delete the MyPreciousWs from the �ook folder and re-execute the whole notebook, to both save a fresh copy of the workspace & to display the correct save message next to the )save command. This commit includes a couple of immaterial changes to code cells which were used to force the re-execution of the (cached) notebook, a workaround that will hopefull be addressed with jupyter-book/jupyter-book#1633. Thoughts for the future include adding a preprocessing step where the MyPreciousWs is always deleted from the �ook folder (to make sure that the command )save always works) or a hidden cell in the notebook that deletes the workspace before saving.
The INDEX ERRORs that were happening arose because the MyPreciousWs that was being loaded in the section about workspaces had been saved, somehow, with ⎕IO ← 0, which meant that loading it was throwing off the remainder of the calculations. Supposedly, this issue would never really arise because the workspace was first being saved from within the notebook, and only then loaded. However, because the workspace already existed in the book folder, the first attempt to )save it was failing: the current workspace was the clear workspace and we were trying to save on top of a named workspace. To fix this, I had to delete the MyPreciousWs from the book folder and re-execute the whole notebook, to both save a fresh copy of the workspace & to display the correct save message next to the )save command. This commit includes a couple of immaterial changes to code cells which were used to force the re-execution of the (cached) notebook, a workaround that will hopefull be addressed with jupyter-book/jupyter-book#1633. Thoughts for the future include adding a preprocessing step where the MyPreciousWs is always deleted from the book folder (to make sure that the command )save always works) or a hidden cell in the notebook that deletes the workspace before saving.
In Chapter 3 there are several index errors (caused by wrong
⎕IOsetting) and some value errors, as shown in the screenshots. (A few errors of course are supposed to be there and on purpose.)I am viewing the book on Safari on macOS 10.14.16 (Mojave). I reloaded the web page.
I have exactly the same problem on the iPad.
The text was updated successfully, but these errors were encountered: