Modify defensive programming section

[bielsnohr]

• Remove explicit use of np.assert_allclose under pytest.raises
• Add Exception message matching to optional exercise

Crucial note: I have not tested this with the project repo code. Not sure when I will get time to do that, but if someone else does have an hour or so to spare, please feel free to verify that the code edits below work.

Closes #108

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/python-intermediate-development/compare/md-outputs..md-outputs-PR-451

The following changes were observed in the rendered markdown documents:

 24-diagnosing-issues-improving-robustness.md | 70 ++++++++++++++++++++++++++--
 md5sum.txt                                   |  2 +-
 2 files changed, 67 insertions(+), 5 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-04-17 14:53:11 +0000

[anenadic]

Looks good to me - thank you @bielsnohr.