IMPORTANT: Doing this for the entire codebase in a single PR would be infeasible to review, and would most likely lead to a large amount of conflicts. Do one module per PR, and reference this issue in the PR (but don't say "fix", just reference the issue).

As we have finally dropped support for Python 3.5, we can now utilize f-strings. It would be a good idea to replace format strings with f-strings, except in the places where we use format strings as templates that are stored in variables. There is a TON of use of str.format in the test suite in particular.

So, all instances on the form "some literal {} string".format(var) should be replaced with f"some literal {var} string". Here's an example of where we should use an f-string instead.

The above should be rewritten as:

description=f"{repo_base_name} created for {student}"

Finding modules with str.format calls: Simply executing grep -r \.format in a shell should net you most occurrences.

Progress (i.e. don't start working on these modules because someone else is):

• _repobee.ext.gitlab: #470 (DONE)