ci: add pep8-naming check to flake8 and ignore a bunch of warnings

[jenhagg]

Purpose

Add pep8-naming check to flake8, so it is run by tox locally and in github.
See https://github.com/Breakthrough-Energy/RenewableEnergyProject/issues/343

What the code is doing

In this case, we ignore almost all the warnings. Note: adding the noqa on some lines also caused black to reformat into multi line declarations, which in turn requires moving the noqa back to the first line in that group. Hopefully we don't have to do this a lot.

Testing

tox -e flake8

Time estimate

5 min

[BainanXia]

Looks good. Thanks for taking care of this.

[danielolsen]

@lanesmith can we come up with some more descriptive variable names for the cost curve visualizations?

[lanesmith]

@lanesmith can we come up with some more descriptive variable names for the cost curve visualizations?

@danielolsen, yeah certainly. What's the best way for me make those additions to this PR? Should I just checkout this branch?

[danielolsen]

@danielolsen, yeah certainly. What's the best way for me make those additions to this PR? Should I just checkout this branch?

I suggest that you check out this branch, create a new branch of your own with your commit(s), and push that. Then @jon-hagg can cherry-pick your commits into this branch when ready, and there's no risk of conflicts.

[lanesmith]

@jon-hagg, I've finished updating the variable names for the cost curve visualization. The updates are in the branch lane/cost_curves_refactor. Let me know how you would like to proceed with this.

[jenhagg]

@jon-hagg, I've finished updating the variable names for the cost curve visualization. The updates are in the branch lane/cost_curves_refactor. Let me know how you would like to proceed with this.

Thanks @lanesmith, probably the easiest way would be to create a PR to this branch, which (when merged) will effectively append your commits to the current PR.

[danielolsen]

Looks good, thanks!