add test to run python-code example in readme

[leifdenby]

Add missing test that ensures that python-code example in README executes without error.

Describe your changes

Add a test which looks for python codeblocks in README and executes them. Having this test will ensure that python codeblock examples in README keep working as the codebase evolves.

No changes to dependencies.

Issue Link

In reviewing #32 I just realised that the example in the README hadn't been updated. I am adding this test to ensure that that should be caught be tests in future.

Type of change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📖 Documentation (Addition or improvements to documentation)

Checklist before requesting a review

• My branch is up-to-date with the target branch - if not update your fork with the changes from the target branch (use pull with --rebase option if possible).
• I have performed a self-review of my code
• For any new/modified functions/classes I have added docstrings that clearly describe its purpose, expected inputs and returned values
• I have placed in-line comments to clarify the intent of any hard-to-understand passages of my code
• I have updated the documentation to cover introduced code changes
• I have added tests that prove my fix is effective or that my feature works
• I have given the PR a name that clearly describes the change, written in imperative form (context).
• I have requested a reviewer and an assignee (assignee is responsible for merging)

Checklist for reviewers

Each PR comes with its own improvements and flaws. The reviewer should check the following:

• the code is readable
• the code is well tested
• the code is documented (including return types and parameters)
• the code is easy to maintain

Author checklist after completed review

• I have added a line to the CHANGELOG describing this change, in a section
  reflecting type of change (add section where missing):
  • added: when you have added new functionality
  • changed: when default behaviour of the code has been changed
  • fixes: when your contribution fixes a bug

Checklist for assignee

• PR is up to date with the base branch
• the tests pass
• author has added an entry to the changelog (and designated the change as added, changed or fixed)
• Once the PR is ready to be merged, squash commits and merge the PR.

[khintz]

Good idea to test the code blocks in the readme.
But you have to be extremely convincing to make me approve without adding an entry to the changelog ;)

[joeloskarsson]

Good idea to add this! lgtm

[khintz]

This looks good. Except for the conflict which has to be fixed of course.