Let’s look at an example: def f(value, key, hash={}): hash[value] = key return hash print(f(‘a’, 1)) print(f(‘b’, 2)) Which you probably expect to output: {‘a’: 1} {‘b’: 2} But actually outputs: {‘a’: 1} {‘a’: 1, ‘b’: 2}
pylint –generate-rcfile shows it like this: [MESSAGES CONTROL] # Enable the message, report, category or checker with the given id(s). You can # either give multiple identifier separated by comma (,) or put this option # multiple time. #enable= # Disable the message, report, category or checker with the given id(s). You # can either … Read more
There are two options I’m aware of. One, change the PYTHONPATH environment variable to include the directory above your module. Alternatively, edit ~/.pylintrc to include the directory above your module, like this: [MASTER] init-hook=’import sys; sys.path.append(“/path/to/root”)’ (Or in other version of pylint, the init-hook requires you to change [General] to [MASTER]) Both of these options … Read more
Pylint message control is documented in the Pylint manual: Is it possible to locally disable a particular message? Yes, this feature has been added in Pylint 0.11. This may be done by adding # pylint: disable=some-message,another-one at the desired block level or at the end of the desired line of code. You can use the … Read more
It is not true for logger statement because it relies on former “%” format like string to provide lazy interpolation of this string using extra arguments given to the logger call. For instance instead of doing: logger.error(‘oops caused by %s’ % exc) you should do logger.error(‘oops caused by %s’, exc) so the string will only … Read more
The idea behind this message is for the sake of readability. We expect to find all the attributes an instance may have by reading its __init__ method. You may still want to split initialization into other methods though. In such case, you can simply assign attributes to None (with a bit of documentation) in the … Read more
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 accepted answer won’t fix the error when importing own modules. Use the following setting in your workspace settings .vscode/settings.json: “python.autoComplete.extraPaths”: [“./path-to-your-code”], Reference: Troubleshooting, Unresolved import warnings
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