# wemake-python-styleguide
**Repository Path**: mirrors_opencollective/wemake-python-styleguide
## Basic Information
- **Project Name**: wemake-python-styleguide
- **Description**: The strictest and most opinionated python linter ever!
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-09-25
- **Last Updated**: 2026-04-05
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
# wemake-python-styleguide
[](https://wemake.services)
[](https://opencollective.com/wemake-python-styleguide)
[](https://travis-ci.org/wemake-services/wemake-python-styleguide)
[](https://coveralls.io/github/wemake-services/wemake-python-styleguide?branch=master)
[](https://pypi.org/project/wemake-python-styleguide/)
[](https://github.com/wemake-services/wemake-python-styleguide)
---
Welcome to the strictest and most opinionated python linter ever.
`wemake-python-styleguide` is actually a [flake8](http://flake8.pycqa.org/en/latest/)
plugin with [some other plugins](https://wemake-python-stylegui.de/en/latest/pages/usage/violations/index.html#external-plugins) as dependencies.
## Quickstart
```bash
pip install wemake-python-styleguide
```
You will also need to create a `setup.cfg` file with the [configuration](https://wemake-python-stylegui.de/en/latest/pages/usage/configuration.html).
We highly recommend to also use:
- [flakehell](https://wemake-python-stylegui.de/en/latest/pages/usage/integrations/flakehell.html) for easy integration into a **legacy** codebase
- [nitpick](https://wemake-python-stylegui.de/en/latest/pages/usage/integrations/nitpick.html) for sharing and validating configuration across multiple projects
## Running
```bash
flake8 your_module.py
```
This app is still just good old `flake8`!
And it won't change your existing workflow.
See ["Usage" section](https://wemake-python-stylegui.de/en/latest/pages/usage/setup.html)
in the docs for examples and integrations.
## What we are about
The ultimate goal of this project is
to make all people write **exactly** the same `python` code.
| | black | mypy | pylint | flake8 | 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:
0. Enforce `python3.6+` usage
1. Significantly reduce 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](https://wemake-python-stylegui.de/en/latest/pages/usage/violations/index.html).
## What we are not
We are *not* planning to do the following things:
0. Assume or check types, use `mypy` together with our linter
1. [Reformat code](https://wemake-python-stylegui.de/en/latest/pages/usage/integrations/auto-formatters.html), since we believe that developers should do that
2. Check for `SyntaxError` or logical bugs, write tests instead
3. Appeal to everyone. But, you can [switch off](https://wemake-python-stylegui.de/en/latest/pages/usage/setup.html#ignoring-violations) any rules that you don't like
## Supporting us
We in [wemake.services](https://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.
[](https://opencollective.com/wemake-python-styleguide)
[](https://opencollective.com/wemake-python-styleguide)
[](https://opencollective.com/wemake-python-styleguide)
## Show your style
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:
[](https://github.com/wemake-services/wemake-python-styleguide)
### Markdown
```md
[](https://github.com/wemake-services/wemake-python-styleguide)
```
### Restructured text
```rst
.. 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!
[](https://github.com/wemake-services/wemake-python-styleguide/graphs/contributors)
See ["Contributing"](https://wemake-python-stylegui.de/en/latest/pages/contributing.html) section in the documentation if you want to contribute.
You can start with [issues that need some help](https://github.com/wemake-services/wemake-python-styleguide/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
right now.