wemakeservices/wemake-python-styleguide repository overview

⁠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

pip install wemake-python-styleguide

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

We highly recommend to also use:

• flakehell⁠ for easy integration into a legacy codebase
• nitpick⁠ for sharing and validating configuration across multiple projects

⁠Running

flake8 your_module.py

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⁠!

⁠What we are about

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

We have several primary objectives:

1. Enforce python3.6+ usage
2. Significantly reduce complexity of your code and make it more maintainable
3. Enforce "There should be one -- and preferably only one -- obvious way to do it" rule to coding and naming styles
4. 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. Reformat code⁠, since we believe that developers should do 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 to 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.