5 ms·
Somewhat offtopic, does anyone have a link to a page that describes which extensions/tools I should be using with VSCode to author Python code? Edited to add:
by bloopernova 3y ago
Somewhat offtopic, does anyone have a link to a page that describes which extensions/tools I should be using with VSCode to author Python code?
Edited to add: when you read various recommendations, they're all discrete and don't have the overall context. e.g. I installed the VSCode suggested extensions, but then read a comment that I should really be using Ruff. OK, that's good, but if I have extensions X, Y, and Z, should I add extensions A, B, and C?
- jimmydoe 3y agothe default extension is good enough to begin with. as you are adding more to your project (e.g. black/isort/django), you can naturally find more extensions.
- chpatrick 3y agoOne nuisance I found is that it's hard to get the VSCode Pyright to apply the same rules as the command-line one, which is very annoying when your IDE says the code is okay but it fails on CI. Not sure if that's fixed yet.
- gen220 3y agoThese pages are naturally out of date from the moment they're written. Caveats aside, I use pyright, ruff and black (although ruff will probably one day consume `black`, entirely) – that's it. `ruff` centralizes a lot of the linter/fixer ecosystem (isort, autoflake, pylint and more). `pyright` is for GoToDefinition and type-checking. `black` is for sanity-checking what `ruff` spits out, and should hopefully not be necessary (for me) as a standalone package at some point in the near future. Ruff is not 1.0 yet, so I wouldn't use it at work – but I use it in all my own things.
- bloopernova 3y agoThank you, that description of each extension and how they work together is exactly what I was looking for. I appreciate you, internet person.