search

swcarpentry / python-novice-inflammation

Programming with Python
http://swcarpentry.github.io/python-novice-inflammation/
Other
303 stars 781 forks source link

always use spaces after commas #1059

Closed edbennett closed 1 year ago

edbennett commented 1 year ago

In both Python and English, it's considered good practice to use a space after a comma.

This PR adjusts both image captions and Python code snippets to consistently put spaces after commas, to demonstrate the style of code we would like people to write

github-actions[bot] commented 1 year ago

Thank you!

Thank you for your pull request :smiley:

:robot: 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:

Rendered Changes

:mag: Inspect the changes: https://github.com/swcarpentry/python-novice-inflammation/compare/md-outputs..md-outputs-PR-1059

The following changes were observed in the rendered markdown documents:

 02-numpy.md      |  4 ++--
 03-matplotlib.md |  4 ++--
 04-lists.md      |  2 +-
 06-files.md      | 10 +++++-----
 08-func.md       |  2 +-
 10-defensive.md  |  2 +-
 12-cmdline.md    |  2 +-
 md5sum.txt       | 14 +++++++-------
 8 files changed, 20 insertions(+), 20 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.

:stopwatch: Updated at 2023-07-27 15:30:53 +0000