E203 is not yet supported in Pylint AFAIK E225 is C0322 / C0323 E251 should be C0322/C0323, but I’m not sure that Pylint does not special case parameters and allows lack of space there E301, E303 are not supported AFAIK E501 is C0301 and you can configure the length in your pylintrc W291, W292 and … Read more
pylint doesn’t know of which type other is (how should it, you can compare an instance of A to everything), therefore the warning. I don’t think there is a way around disabling the warning. You can disable the warning for only that one line with appending # pylint: disable=W0212 to that line.
I figured out how to do this. Add this line to your settings: “python.linting.pep8Args”: [“–max-line-length=100”],
Generalized use of global variables can make maintenance a nightmare, because they make tracing the flow of your program, and sometimes you get weird bug, because some module has read the variable and acted on its value before some other module changed the value of the variable (and this can result from inverting two import … Read more
You can globally disable warnings of a certain class using pylint –disable=W1234 or by using a special PyLint configuration file pylint –rcfile=/path/to/config.file A sample config file is given below: [MESSAGES CONTROL] # C0111 Missing docstring # I0011 Warning locally suppressed using disable-msg # I0012 Warning locally suppressed using disable-msg # W0704 Except doesn’t do anything … Read more
As far as I’m aware you can’t disable specific warnings for entire directories or files. However, you can disable all warnings for specific directories using the following on the command line: –ignore=<file[,file]> The file here can be a directory. Personally, and I know you said you’d rather not, I’d add a disable to the top … Read more
Take a look at the pylint/epylint.py file which contains two different ways to start Pylint programmatically. You can also simply call from pylint.lint import Run Run([‘–errors-only’, ‘myfile.py’]) for instance.
Summarizing all answers. This is a security measure to not load non-default C extensions. You can white-list specific extension(s). Open user settings and add the following between {}: “python.linting.pylintArgs”: [ “–extension-pkg-whitelist=extensionname” // comma separated ] You can allow to “unsafe load” all extensions. Open user settings and add the following between {}: “python.linting.pylintArgs”: [ “–unsafe-load-any-extension=y” … Read more
The answer to your question’s title is “yes”: I recommend never using from … import *, and I discussed the reasons in another very recent answer. Briefly, qualified names are good, barenames are very limited, so the “third option” is optimal (as you’ll be using qualified names, not barenames) among those you present. (Advantages of … Read more
It seems, from Python docs and experimenting, that relative imports (involving ., .. etc) only work if the importing module has a __name__ other than __main__, and further, the __name__ of the importing module is pkg.module_name, i.e., it has to be imported from above in the directory hierarchy (to have a parent pkg as part … Read more