Hi @funnelweb,
Just to complete @Daniel_Meppiel’s answer, we previously had a stronger integration of Pylint. Every Pylint rule was displayed in SonarQube/SonarCloud. This was creating some confusion as you had to activate Pylint rules in Pylint configuration and SonarQube/SonarCloud quality profile. Thus we decided to simplify Pylint integration. Its rules don’t appear in SonarQube anymore, but Pylint reports can still be imported. You only need to activate the rules in Pylint configuration.
Note however that we improved SonarQube/SonarCloud/SonarLint python analyzer a lot during the last two years. We believe that in most cases, projects won’t need Pylint or any other linter.
If you want to be PEP8 compliant I recommend to import issues from flake8 and activate styling rules. Our python analyzer focuses mostly on bugs, vulnerabilities and code smells, not on styling.
Cheers,
Nicolas