Allow fne-grain control of bad-whitespace warnings

[pylint-bot]

Originally reported by: Edd Barrett (BitBucket: vext01, GitHub: @vext01?)

---

It would be neat if it was possible to have more control over the bad-whitespace warnings.

For example, consider the following:

j = [ x for x in y if x > 4 ]
def myfunc(a,b,c):
    ...

bad-whitespace is fired because:

• There is a space after the opening [
• There is a space before the closing ]
• There is no space after the commas separating function parameters.

Ideally I would like to disable the first two warnings whilst retaining the third. Currently bad-whitespace covers all of the above warnings. It would be neat to have a bad-whitespace-listcomps, bad-whitespace-paramcommas, ...

What do you think?

Thanks :)

---

• Bitbucket: https://bitbucket.org/logilab/pylint/issue/246

[pylint-bot]

Original comment by BitBucket: rneu31, GitHub: @rneu31?:

---

I agree completely. I have a specific use case for avoiding the bad-whitespace warning for requiring one space after a comma.

I am doing C/C++ Unit Tests using an in house framework where I want to align the columns of inputs. I have written a currently in house wrapper for Pylint and pep8 tools that will soon have some configuration options for which use case the tool is invoked for.. I.E Python source code or C/C++ Unit Tests. I would like to be able to disable the specific error for the case where I am running Pylint across a Unit Test.

#!python

case_list = [
    ('description here',
     0x1234, 0x3459, False, True, '0xABCD'),

    ('description here',
     0,      1,      2,     3,    4
]

[darksuji]

Another case that belongs in its own warning class is spaces in kwargs.

def f(i = 0):

and

f(i = 4)

both trigger bad-whitespace. Accordingly, you can't use spaces in kwargs unless you're also willing to turn off warnings telling you to use spaces around non-kwargs-associated operators.

[moylop260]

There is a pep related with this request?

[PCManticore]

What do you mean by a PEP? This issue is about having the ability to ignore certain classes of errors regarding bad-whitespace. While we might enforce PEP8 by default, which we fully don't, having the ability to configure pylint to your own style is pretty valuable.

[moylop260]

I got it
Thank for clarify