Question: When importing pygame pylint is going crazy:

```
E1101:Module 'pygame' has no 'init' member
E1101:Module 'pygame' has no 'QUIT' member

```

I have searched the net and I have found this:

```
"python.linting.pylintArgs": ["--ignored-modules=pygame"]

```

It solves the problem with pygame, but now pylint is going crazy in other way: [crazy\_pylint.png](https://i.stack.imgur.com/qyC6r.png).
Then I have found `"python.linting.pylintArgs": ["--ignored-files=pygame"]`, but what it does is completely disabling pylint for the whole directory I am working in.
So how do I say pylint that everything is OK with pygame?

Answer: 
For a specific binary module you can whitelist it for pylint. For the pygame module it would be as follows:

```
{
    "python.linting.pylintArgs": [
        "--extension-pkg-whitelist=pygame"
    ]
}

```
OP You can also maintain the pylint pygame fix you found in vscode by including the vscode default arguments yourself. 
The linter is going nuts (crazy\_pylint.png) because you were clobbering the default pylint arguments with your own custom `python.linting.pylintArgs`.
The pygame module ignore fix does work, and the linter can return to non-crazy mode by also including the clobbered default arguments in your own custom `python.linting.pylintArgs`.

From the docs:

> 
> These arguments are passed whenever the python.linting.pylintUseMinimalCheckers is set to true (the default). 
>  If you specify a value in pylintArgs or use a Pylint configuration file (see the next section), then pylintUseMinimalCheckers is implicitly set to false.
> 
> 
> 

The defaults vscode passes according to this: <https://code.visualstudio.com/docs/python/linting> are:

```
    --disable=all,
    --enable=F,E,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode

```

So, here is how to pass all those defaults as well as the `--ignored-modules=pygame` in user settings within vscode:

```
    "python.linting.pylintArgs": [
        "--disable=all",
        "--enable=F,E,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode",
        "--ignored-modules=pygame"
    ]

```

Per @C.\_ comment above, he's definitely speaking truth; the linter will help! 

I'm writing better code with it enabled for sure. 

Also, I discovered that you can further fine-tune your pylinter with the enable line and comma delimited "readable pylint messages" 
listed here: <https://github.com/janjur/readable-pylint-messages/blob/master/README.md>

So to not ignore also trailing-newlines, you would append the `enable=` list argument to include simply `trailing-newlines`.

I really hope this helps you OP :) It helped me! 

Thanks for asking the question, and sharing `--ignored-modules`.