We’ve just added a new blog post about Python analysis:
For a lot of years, SonarSource implemented a few Python rules, calculated metrics, and displayed coverage, but mainly we just wrapped PyLint and called it a day. There’s no real shame in that; PyLint is a mainstay and a lot of folks rely on it. But now we’ve realized that “okay” isn’t good enough. So we’ve set a goal for 2020. By the end of the year, SonarQube, SonarCloud, and SonarLint should be your go-tos for Python Code Quality and Security. In other words, our Python analysis will be Kicking Asp and Taking Names. (See what I did there? :-D)…