Improve VS Code Python settings #2860
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The python.formatting.provider setting was deprecated in favor of having a separate extension for each Python formatter and using editor.defaultFormatter instead. This adds a recommendation for the Black formatter extension and selects it for Python files.
This limits vscode's Python analysis to the scripts folders so it doesn't slow down trying to scan all of Zephyr.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed the deprecated
python.formatting.providersetting and switched to using correct extension for formatting Python files now that different formatters have been broken out into separate extensions.Limited Python analysis to only the directories containing Python scripts, so VS Code doesn't slow down while scanning all of Zephyr.
PR check-list