Fix recently added PEP8 violations

[stvstnfrd]

These violations were introduced recently, after we had removed all
instances of these violations. As of now, these represent the final PEP8
violations.

This PR also drops the PEP8 threshold down to zero violations (!!!), so
it will need to be merged after #6045 lands.

[openedx-webhooks]

Thanks for the pull request, @stvstnfrd! I've created OSPR-237 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.

Feel free to add as much of the following information to the ticket:

• supporting documentation
• edx-code email threads
• timeline information ('this must be merged by XX date', and why that is)
• partner information ('this is a course on edx.org')
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the Github pull request interface. As a reminder, our process documentation is here.

[sarina]

w0rd. Although there may be a bug in the violations script you need to address - perhaps the quality build is failing because it is a "<" rather than "<="? Ping me when it's good and I'll take a final look.

[stvstnfrd]

@sarina The quality test is passing again. It turned out that someone
else had snuck 2 more PEP8 violations into the code while this PR was
in flight.

[sarina]

how is that possible with diff-quality!?!? Will merge if/when build passes. Thanks!

[stvstnfrd]

Yeah, I don't know either, but I'm looking at it, clear as day [1].

Aren't test failures just a "suggestion" and not actually a blocker on
merge? Too bad we don't have commit hooks...

Anyway, tests are passing.

[1] https://github.com/edx/edx-platform/pull/6073/files#diff-35e1eec9376ca44d4faa41efb1d32750R178

[jzoldak]

😍