Skip to content

A number of small nitpicks changes to the temperature function examples#1116

Open
edbennett wants to merge 2 commits intoswcarpentry:mainfrom
edbennett:nitpick-temperatures
Open

A number of small nitpicks changes to the temperature function examples#1116
edbennett wants to merge 2 commits intoswcarpentry:mainfrom
edbennett:nitpick-temperatures

Conversation

@edbennett
Copy link
Copy Markdown
Contributor

This PR introduces a small number of related changes to the temperature examples for functions

  1. Use temp_f rather than temp, to consistently identify that the input temperature for fahr_to_celsius is a temperature in Fahrenheit, since the return value will also be a temperature.
  2. Use "kelvins" rather than "Kelvin"; since the kelvin is an SI unit, using lowercase and plural is correct.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 23, 2026

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/swcarpentry/python-novice-inflammation/compare/md-outputs..md-outputs-PR-1116

The following changes were observed in the rendered markdown documents:

 08-func.md              |  55 +++++++++---------
 fig/python-function.svg | 149 ++++++++++++++++++++++++++++++++++++++++++------
 md5sum.txt              |   2 +-
 3 files changed, 159 insertions(+), 47 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-04-23 13:15:28 +0000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant