Pylint: ignore TODO comments

[singingwolfboy]

TODO comments are currently flagged by pylint, which causes them to break the build on Jenkins. We have many TODO comments already in the codebase, and it isn't practical to stop working to fix them all. We also don't want to just delete them: they contain valuable information. However, anytime that code is touched, diff-quality flags the TODO and fails the build.

It would be nice if there were a way to have diff-quality report on these TODO comments, but more as a warning, and not have them fail the build. However, I don't know how to do that, so this is the next best solution. TODO comments and similar can always be caught by humans in code review.

[singingwolfboy]

@andy-armstrong @jzoldak: you two are probably interested in having a discussion on this pull request.

[jzoldak]

This is TE-564
I think a better way to go about it is the approach outlined there, namely to see if we can change the paver run_quality command to add --disable=W0511

[singingwolfboy]

@jzoldak That's fine with me. I've changed it in this PR. Can I get a thumbs-up?

[jzoldak]

@singingwolfboy did you test that it works as expected?

[singingwolfboy]

I was editing the wrong task -- thanks for pointing that out, @jzoldak. I've added it to run_quality and removed it from run_pylint. (Or do we want it on run_pylint too?) I've tested it on devstack, and it seems to work correctly.

[andy-armstrong]

👍 Thanks for tackling this, @singingwolfboy.

[benpatterson]

LGTM 👍

[benpatterson]

When you merge, could you put TE-564 in the commit message?

[benpatterson]

Ah you are too quick. No big deal.