Dear VSCode users,
with this new SonarLint for VSCode release, we’ve introduced quick fixes for Python - in addition to Java, JavaScript, TypeScript, C and C++.
You can browse all our Python detections here and those already providing quick fixes here; we’re going to support quick fixes for more and more rules over the next releases.
In order to apply a quick fix provided by SonarLint, you can simply use the keyboard shortcuts you are already used to for VSCode Code Actions or you can hover with the mouse over an issue.
Python quick fixes are available to all VSCode users using SonarLint alone or in connected mode with SonarCloud 
.
If you use SonarLint in connected mode with SonarQube 
, the quick fixes will become available for you once the next SonarQube version (9.6) will be released.
If you work in a team or in a company using already SonarQube or SonarCloud, we strongly recommend you to use SonarLint in connected mode, as you will automatically benefit of the following:
- the Quality Profile (active/inactive rules) configured for your project in SonarQube or SonarCloud are replicated and applied to the SonarLint local analysis
- the status of issues is synchronized, so for example, if another contributor mutes an issue in SonarQube, that issue will stop being displayed in VSCode as well
- the analysis parameters configured for your project in SonarQube or SonarCloud, for example excluding specific files or directories, are also synced and applied to the SonarLint local analysis in VSCode
Before this release, setting up the connected mode required manually modifying the VSCode settings.json file at user level. We’ve been working to make this process easier and more intuitive for you; as a result SonarLint UI now guides you to set up the connection.
In the near future, we’ll also work to eliminate the need to specify the sonarlint.connectedMode.project.projectKey in the settings.json file at workspace level, so that the entire process will be as smooth and quick as possible. Stay tuned!