[andrewgait]

Resolves #120

[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/UoMResearchIT/Programming-With-Python/compare/md-outputs..md-outputs-PR-131

The following changes were observed in the rendered markdown documents:

 01-introduction.md                |  4 ++--
 02-dictionaries.md                |  4 ++--
 03-numpy_essential.md             |  4 ++--
 04-defensive_programming.md       |  4 ++--
 05-units_and_quantities.md        |  4 ++--
 06-pandas_essential.md            |  4 ++--
 07-software_package_management.md |  4 ++--
 md5sum.txt                        | 14 +++++++-------
 8 files changed, 21 insertions(+), 21 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 2026-11-13 10:51:05 +0000

[github-actions]

Changes were made to copyright notices

There are copyright updates on the (temporary) add-license-headers-to-120-fix-progress-bar-at-head-of-course-notes-2026-11-13-10-50-25 branch. Please review and merge, or add further commits (this branch will be deleted).

[Scottan]

Looks good to me. Not been able to test whether it fixes the problem, but changes are sensible and should be included either way, we can test if the site is fixed once it gets rebuilt from the develop branch