WIP: Correct Pylint violations - #7008
Conversation
I can find no other record of this class.
|
Thanks for the pull request, @stvstnfrd! I've created OSPR-410 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:
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. |
|
oof! lots of test failures. Already this has merge conflicts, and I am going to assume that we should merge in #6998 before continuing, no? It might be easier to split up these violations into separate PRs, especially given the wealth of test failures. |
|
for some reason, Jenkins is being a butt. This was your most recent build. |
|
Yes, we can merge #6998 before this. The funny thing is that I already pulled much out of this PR, but you're right; it'll probably make sense to split this out further. I'll rebase, take and look at test failures, and probably start splitting out some of these commits. I'll ping you again when this is ready. |
|
This is getting supplemented by newer, smaller PRs so I'm going to close this one. |
No description provided.