cleanup: f-string formatting

[zabop]

As discussed here, code in this repo appears directly in the documentation. (An example, there are hundreds.) This commit introduces f-strings to increase readability of both code and documentation.

Fixes #785 🦕

[zabop]

I am not sure why 2 tests failed, let me know if further input is needed from me.

[unforced]

Yep, for the conventionalcommits message, you just need to amend the commit message to be "cleanup: f-string formatting". I thought editing the title there would do it, but seems not.
For the other one, you can run nox -s blacken lint and it'll lint cleanup all the files.
If you're not able to do either of those, let me know and I can help.

[Mariatta]

Thank you. Mostly looks correct, except for a few spots.

[zabop]

@Mariatta, thank you, great catches!
@Breathtender, I get an error with nox:

% nox -s blacken lint
nox > Running session blacken
nox > Session blacken skipped: Python interpreter 3.8 not found.
nox > Running session lint
nox > Session lint skipped: Python interpreter 3.8 not found.
nox > Ran multiple sessions:
nox > * blacken: skipped
nox > * lint: skipped

Which I do not yet know how to solve. My Python interpreter seems to be Python 3.8 (screenshot of pottom right corner of PyCharm):

[unforced]

Oh that's strange. I'll check on why that's happening. For now I'll just run the lint myself and add the commit, once you push up your changes to address @Mariatta's comments.

[zabop]

@Breathtender, just read your reply now, sorry; in the meantime I figured out what's going on and were able to run nox -s blacken lint. Just pushed the results.

[zabop]

Addressing @Mariatta suggestions now...

[zabop]

I think I have addressed the suggestions.

My last commit was the result of a typo & forgetting to run nox -s blacken lint before. Do I have to keep the cleanup: f-string formatting commit messages when I push fixes to an already open PR, or is more freedom allowed here? (To rephrase the question: which commit message is checked by the conventionalcommits test?) I used the remove unnecessary :d specifier commit message to approve @Mariatta suggestions, I hope that's ok.

[unforced]

No, it'll automatically roll all your commits together, and so the first commit message is ultimately the one that matters.

[unforced]

Thanks for making those adjustments! I'll wait for @Mariatta's approval on the changes requested, but this is looking good to me.

[Mariatta]

Thanks! LGTM