* Corrected small typos around resistor bands.
* Due to failing CI, alterations to the test generator script were needed.
The generated vs submitted diff now skips the first three lines of the file
so that the generation date is not picked up and flagged as needing regeneration.
Sadly, a workaround was also needed to prevent Python difflib from noting the difference
anyways and producing an empty "false positive" diff.
All templates and test files also needed to be altered to ensure that the first three
lines of every test file will always be the autogeneration comment and date.
Hopefully, this will now stop the CI failures without creating any subtle additional bugs.
* Touch up to bowling template. Added back the error raising utility.
* Touch up to two-bucket template to add back in error raising utility.
[no important files changed]
* Additional sweep to update Python versions and supported Python versions.
* Fixed requirements and CONTRIBUTING.
* Trying a different line skip to see if it fixes CI. CI is failing on test file generation again.
* Once again re-rendering tests to see if it fixes CI.
[no important files changed]
* Changed generate script to skp diffing generated comments and timestamp at top of file.
* Reordered and regenerated test files for practice exercises.
[no important files changed]
* Corrected the macro for comments on the test file.
* Added current_date (utcnow()) variable available for template macros.
* Removed unnecessary datetime import from macros file.
* Regenerated all practice exercise test files to add timestamp.
* Changed `datetime.now(tz=timezone.utc)` to `datetime.now(tz=timezone.utc).date()`
* Second regeneration to remove `timestamp` and just keep `date` for test files.
[no important files changed]
The original code passed a generator expression into the assertion,
which was converted into a list prior to being evaluated for truthiness.
If all the values in the generator are False, the assertion will check
whether `[False, False, False, ...]` is truthy, which it is.
I can't see how this test can ever have failed.
I've used `subTest()`, having seen it used in other exercises.
- Added a skip formatting instruction to Black
- Reformatted template to have assert test all on one line
- Re-generated tests and tested example solution
