Flake8
black
Our great sponsors
Flake8 | black | |
---|---|---|
32 | 321 | |
3,231 | 37,210 | |
2.1% | 3.1% | |
7.5 | 9.5 | |
3 days ago | 1 day ago | |
Python | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Flake8
-
Enhance Your Project Quality with These Top Python Libraries
Flake8. This library is a wrapper around pycodestyle (PEP8), pyflakes, and Ned Batchelder’s McCabe script. It is a great toolkit for checking your code base against coding style (PEP8), programming errors (like SyntaxError, NameError, etc) and to check cyclomatic complexity.
- Django Code Formatting and Linting Made Easy: A Step-by-Step Pre-commit Hook Tutorial
-
Enhancing Python Code Quality: A Comprehensive Guide to Linting with Ruff
Flake8 combines the functionalities of the PyFlakes, pycodestyle, and McCabe libraries. It provides a streamlined approach to code linting by detecting coding errors, enforcing style conventions, and measuring code complexity.
-
Which is your favourite or go-to YouTube channel for being up-to-date on Python?
He made yesqa and pyupgrade (among others), and also works on flake8. His main job is for https://sentry.io/.
-
The Power of Pre-Commit for Python Developers: Tips and Best Practices
repos: - repo: https://github.com/psf/black rev: 21.7b0 hooks: - id: black language_version: python3.8 - repo: https://github.com/PyCQA/flake8 rev: 3.9.2 hooks: - id: flake8
-
Is it considered rude to completely change the formatting of someone else's code when making a PR?
https://github.com/psf/black it’s a PEP8 compliant formatter for Python codebases. If you don’t like auto formatting files you can use https://github.com/PyCQA/flake8 it just lists out all of the style issues so you can fix them manually.
-
Ruff: one Python linter to rule them all
I have no stake in that, but my observation is that the actual discussion appears to have both supporters and detractors rather than overwhelming support. Either way, it has nothing to do with whether or not it is realistic to say that Ruff is the "one Python linter to rule them all".
- Improve your Django Code with pre-commit
- Even the Pylint codebase uses Ruff
black
-
Enhance Your Project Quality with These Top Python Libraries
Black: Known as “The Uncompromising Code Formatter”, Black automatically formats your Python code to conform to the PEP 8 style guide. It takes away the hassle of having to manually adjust your code style.
-
Uv: Python Packaging in Rust
black @ git+https://github.com/psf/black
-
Let's meet Black: Python Code Formatting
In the realm of Python development, there is a multitude of code formatters that adhere to PEP 8 guidelines. Today, we will briefly discuss how to install and utilize black.
-
Show HN: Visualize the Entropy of a Codebase with a 3D Force-Directed Graph
Perfect, that worked, thank you!
I thought this could be solved by changing the directory to src/ and then executing that command, but this didn't work.
This also seems to be an issue with the web app, e.g. the repository for the formatter black is only one white dot https://dep-tree-explorer.vercel.app/api?repo=https://github...
- Introducing Flask-Muck: How To Build a Comprehensive Flask REST API in 5 Minutes
-
Embracing Modern Python for Web Development
Ruff is not only much faster, but it is also very convenient to have an all-in-one solution that replaces multiple other widely used tools: Flake8 (linter), isort (imports sorting), Black (code formatter), autoflake, many Flake8 plugins and more. And it has drop-in parity with these tools, so it is really straightforward to migrate from them to Ruff.
-
Releasing my Python Project
1. LICENSE: This file contains information about the rights and permissions granted to users regarding the use, modification, distribution, and sharing of the software. I already had an MIT License in my project. 2. pyproject.toml: It is a configuration file typically used for specifying build requirements and backend build systems for Python projects. I was already using this file for Black code formatter configuration. 3. README.md: Used as a documentation file for your project, typically includes project overview, installation instructions and optionally, contribution instructions. 4. example_package_YOUR_USERNAME_HERE: One big change I had to face was restructuring my project, essentially packaging all files in this directory. The name of this directory should be what you want to name your package and shoud not conflict with any of the existing packages. Of course, since its a Python Package, it needs to have an __init__.py. 5. tests/: This is where you put all your unit and integration tests, I think its optional as not all projects will have tests. The rest of the project remains as is.
-
Lute v3 - installed software for learning foreign languages through reading
using pylint and black ("the uncompromising code formatter")
-
Testing Python Code Using UnitTest
It was with this test that I made that I was able to test my parse_md function, previously called check_md_and_write, and locate a bug that I uncovered a last week. I noticed this bug when I was using the linter, Ruff, and formatter, Black, I set up for my project. If you're interested in reading about the linter and formatter I chose and the setup process you can read last week's blog. Essentially the problem was that I could not parse any Markdown in my program. I wasn't sure what the problem was, but I think it had something to do with when I refactored my code and tried to clean things up. Luckily, I still has the branches where I worked on improved the function to parse markdown and the refactoring branch. To make note of it, I made an issue for myself and specified which branches to take a look at.
-
FastAPI Production Setup Guide 🏁⚡️🚀
Whenever I start a new project I like to maintain quality standards and using automated quality tools makes it easy. Lets go ahead and install mypy for static type checking, black for formatting, and ruff for linting. Add these to the dev dependencies.
What are some alternatives?
Pylint - It's not just a linter that annoys you!
autopep8 - A tool that automatically formats Python code to conform to the PEP 8 style guide.
black - The uncompromising Python code formatter [Moved to: https://github.com/psf/black]
prettier - Prettier is an opinionated code formatter.
yapf - A formatter for Python files
pylama - Code audit tool for python.
autoflake - Removes unused imports and unused variables as reported by pyflakes
ruff - An extremely fast Python linter and code formatter, written in Rust.
prospector - Inspects Python source files and provides information about type and location of classes, methods etc
isort - A Python utility / library to sort imports.