Prohibit wildcard import in pylint
Motivation and context
In python, wildcard imports like from x import * can unpredictably pollute namespace with symbols that are not really expected. In most cases it's better to use import x as y to get access to all module symbols. For popular libraries importable contents of modules are typically maintained well, but it requires quite a lot of work. Currently, we don't use wildcard imports for anything in the project and I can't currently think of places where it could really be useful, so I think it's best to just prohibit their use entirely.
How has this been tested?
Checklist
-
I submit my changes into the developbranch -
I have created a changelog fragment -
I have updated the documentation accordingly -
I have added tests to cover my changes -
I have linked related issues (see GitHub docs) -
I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)
License
-
I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Summary by CodeRabbit
-
Chores
- Updated Pylint configuration to modify linting rules for wildcard imports and logging arguments.
- Adjusted message settings to enable additional code quality checks.