
Whenever as a programmer we start a new project (in any language), we are required to set up an environment for our project to run. The environment...
For further actions, you may consider blocking this person and/or reporting abuse
There's also one more thing that you can add to this amazing setup: linting!
VSCode can automatically find bugs, refactoring opportunities, and things to improve inside your code. I recommend to use
flake8
+wemake-python-styleguide
. Here's how to set things up: code.visualstudio.com/docs/python/...And don't forget to check out
wemake-python-styleguide
on its own. It is the strictest Python linter out there:The strictest and most opinionated python linter ever!
wemake-python-styleguide
Welcome to the strictest and most opinionated Python linter ever.
wemake-python-styleguide
is actually a flake8 plugin with some other plugins as dependencies.Quickstart
You will also need to create a
setup.cfg
file with the configuration.Try it online!
We highly recommend to also use:
Running
This app is still just good old
flake8
And it won't change your existing workflow.See "Usage" section in the docs for examples and integrations.
We also support GitHub Actions as first class-citizens Try it out!
Strict is the new cool
Strict linting offers the following benefits to developers and companies:
I have already added
pylint
for code linting. Choosingformatter
andlinter
is I believe a personal choice. This post is just about how to get started and not a discussion around python linters.On a personal note, thanks for sharing this, I will definitely give it a try for one of my side projects :)
Hi there good day dear Idris -many thanks for this great article - i am going through it all - since i now want to stick with VSCode (note i am on MX-Linux so i just picked VScodium )
hopefully i can do all the things you did - on vscodium too - this would be great!!
i like your ideas and thoughts that you share here - i will go this pathway - and install all the packages you suggest.
Ahhh!!! I wanted to write exactly the same topic. 😤
Haha... I would recommend you to still write a post for the same.
Everyone has a different style of expressing and even different style of understanding. Maybe the style in which you write will help other community members.
Also, you might have different settings in vscode which we might learn from you ☺️
Always write what you feel! 😉
Cool! I did it, like, two days ago! However, I didn't know if it was right... Thanks anyway!
Cool. Share your thoughts if you tried something different for the community.