Update clockscript.py (Sourcery refactored)

[sourcery-ai]

Pull Request #538 refactored by Sourcery.

Since the original Pull Request was opened as a fork in a contributor's
repository, we are unable to create a Pull Request branching from it.

To incorporate these changes, you can either:

1. Merge this Pull Request instead of the original, or

2. Ask your contributor to locally incorporate these commits and push them to
   the original Pull Request

   Incorporate changes via command line

   git fetch https://github.com/curly60e/pyblock pull/538/head
   git merge --ff-only FETCH_HEAD
   git push

NOTE: As code is pushed to the original Pull Request, Sourcery will
re-run and update (force-push) this Pull Request with new refactorings as
necessary. If Sourcery finds no refactorings at any point, this Pull Request
will be closed automatically.

See our documentation here.

Run Sourcery locally

Reduce the feedback loop during development by using the Sourcery editor plugin:

• VS Code
• PyCharm

Help us improve this pull request!

[sourcery-ai]

Lines 147-147 refactored with the following changes:

• Replace call to format with f-string. (use-fstring-for-formatting)

[sourcery-ai]

Sourcery Code Quality Report

Merging this PR leaves code quality unchanged.

Quality metrics	Before	After	Change
Complexity	13.10 🙂	13.10 🙂	0.00
Method Length	108.88 🙂	108.88 🙂	0.00
Working memory	15.03 😞	15.03 😞	0.00
Quality	42.57% 😞	42.57% 😞	0.00%

Other metrics	Before	After	Change
Lines	149	152	3

Changed files	Quality Before	Quality After	Quality Change
pybitblock/clockscript.py	42.57% 😞	42.57% 😞	0.00%

Here are some functions in these files that still need a tune-up:

File	Function	Complexity	Length	Working Memory	Quality	Recommendation
pybitblock/clockscript.py	design	19 😞	495 ⛔	21 ⛔	20.22% ⛔	Refactor to reduce nesting. Try splitting into smaller methods. Extract out complex expressions
pybitblock/clockscript.py	rectangle	4 ⭐	79 🙂	13 😞	62.82% 🙂	Extract out complex expressions

Legend and Explanation

The emojis denote the absolute quality of the code:

• ⭐ excellent
• 🙂 good
• 😞 poor
• ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.

---

Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!