-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS Code Python Formatting #34475
VS Code Python Formatting #34475
Conversation
PR #34475: Size comparison from 8306353 to 5bd315f Full report (46 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, linux, mbed, nxp, psoc6, qpg, stm32, tizen)
|
5bd315f
to
8424879
Compare
PR #34475: Size comparison from 8306353 to 8424879 Full report (82 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nxp, psoc6, qpg, stm32, telink, tizen)
|
Why not go straight for ruff and skip autopep8 and isort ? Also 132 characters for Python code is not very common. Most projects choose 100 or even 88 characters... Just my 2 cents as I have always wondered a bit why the python code in the sdk is not exactly pep formatted. We can do a PR to adjust it but it will also mean a very large diff as all code will be re-formatted. |
|
* add python formatter arguments to vscode .settings * add python formatters to recommended Extensions
* add python formatter arguments to vscode .settings * add python formatters to recommended Extensions
autopep8
andisort
as recommended extensions when installing a new VSCode workspace (sinceisort
is also part of restyled settings Add isort formatter to restyled configuration #24148)