wemake-python-styleguide

wemake-python-styleguide

---

Welcome to the strictest and most opinionated Python linter ever.

wemake-python-styleguide is actually a flake8 plugin, the only one you will need as your ruff companion.

Fully compatible with ALL rules and format conventions from ruff.

Quickstart

pip install wemake-python-styleguide

You will also need to create a setup.cfg file with the configuration.

Try it online!

We highly recommend to also use:

• ondivi for easy integration into a legacy codebase

Running

flake8 your_module.py --select=WPS

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!

Can (and should!) be used with ruff:

ruff check && ruff format
flake8 . --select=WPS

See example ruff configuration in our pyproject.toml.

Strict is the new cool

Strict linting offers the following benefits to developers and companies:

1. Ensures consistency - no matter who works on it, the end product will always be the same dependable code
2. Helps avoid potential bugs - strict rules make sure that you don't make common mistakes
3. Efficient code reviews - each piece of code has a similar familiar style and syntax. If it passes all the checks, there's little left to review!
4. Fewer code revisions - strict linting ensures that you don't have to re-write the codebase again and again
5. Reduce code redundancy - Sometimes we write complex code as we are thinking in a certain way about a problem. The linter offers suggestions that can help simplify the code and eliminate redundant statements

What we are about

The ultimate goal of this project is to make all people write exactly the same Python code.

	flake8	pylint	black	mypy	ruff	wemake-python-styleguide
Formats code?	❌	❌	✅	❌	✅	❌
Finds style issues?	🤔	✅	🤔	❌	✅	❌
Finds bugs?	🤔	✅	❌	✅	✅	✅
Finds complex code?	❌	🤔	❌	❌	✅	✅
Has a lot of strict rules?	❌	🤔	❌	❌	✅	✅
Has a lot of plugins?	✅	❌	❌	🤔	❌	✅

We have several primary objectives:

1. Significantly reduce the complexity of your code and make it more maintainable
2. Enforce "There should be one -- and preferably only one -- obvious way to do it" rule to coding and naming styles
3. Protect developers from possible errors and enforce best practices

You can find all error codes and plugins in the docs.

What we are not

We are not planning to do the following things:

1. Assume or check types, use mypy together with our linter
2. Format code or produce stylistic errors, use ruff format for that
3. Check for SyntaxError or logical bugs, write tests instead
4. Appeal to everyone. But, you can switch off any rules that you don't like

Supporting us :tada:

We in wemake.services make all our tools open-source by default, so the community can benefit from them. If you use our tools and they make your life easier and brings business value, you can return us a favor by supporting the work we do.

Show your style :sunglasses:

If you use our linter - it means that your code is awesome. You can be proud of it! And you should share your accomplishment with others by including a badge in your README file. It looks like this:

Markdown

[![wemake-python-styleguide](https://img.shields.io/badge/style-wemake-000000.svg)](https://github.com/wemake-services/wemake-python-styleguide)

Restructured text

.. image:: https://img.shields.io/badge/style-wemake-000000.svg
   :target: https://github.com/wemake-services/wemake-python-styleguide

Contributing

We warmly welcome all contributions!

See "Contributing" section in the documentation if you want to contribute.

You can start with issues that need some help right now.