Usability: Python Analyzer should not give Trailing whitespace feedback for web sessions

[joshgoebel]

Recommended
Line 25 [C0303 trailing-whitespace] : ["Trailing whitespace"] was reported by Pylint.

Which means this code doesn't follow general [code style](https://www.python.org/dev/peps/pep-0008/) conventions. While this type of issue generally doesn't affect the way code executes, it can hurt readability or the performance of automated tools such as documentation generators or test runners.

I find these warnings quite frustrating when using the web editor.

• There is no auto-correction of trailing whitespace. (it won't fix itself)
• There is no visual indication of trailing whitespace in the editor. (I'll never know until AFTER)
• On the web there is no value IMHO in going back and fixing these one by one by line number.
• It's the kind of problem that keeps breaking over and over (since you can't see it or auto-correct it)

To me this type of feedback is a LOT more useful if someone is using VS Code (or antoher editor)... in that case it makes sense to say "hey, this is problem" because they have so many remedies and it's a more "real" environment - and this is an indication their environment isn't setup for serious Python editing. For students just trying to get started and learning Python via the web editor I think this only gets in the way. For some reason I'm constantly adding trailing whitespace (it happens over and over) so even if I fixed it it would come right back in the next iteration.

[MondoBurrito]

I agree 100%. These errors are so incredibly annoying.

[BethanyG]

@ErikSchierboom or @iHiD -- could you move this to the Python Analyzer repo? I'll take a look at either disabling the rule, or changing the messaging to being non-essential and suggestive. Many thanks!