black
isort
Our great sponsors
black | isort | |
---|---|---|
321 | 41 | |
37,210 | 6,281 | |
3.1% | 1.2% | |
9.5 | 7.7 | |
1 day ago | 8 days ago | |
Python | Python | |
MIT License | 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.
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.
isort
-
Enhance Your Project Quality with These Top Python Libraries
isort: This library sorts your imports alphabetically, and automatically separates them into sections and by type. It provides a cleaner and more organised way to manage project imports.
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
isort will sort the imports for you
-
Django Code Formatting and Linting Made Easy: A Step-by-Step Pre-commit Hook Tutorial
isort is a Python utility that helps in sorting and organizing import statements in Python code to create readable and consistent code. It automatically formats import statements in accordance with PEP 8.
-
How to Write Impeccably Clean Code That Will Save Your Sanity
repos: - repo: https://github.com/ambv/black rev: 23.3.0 hooks: - id: black args: [--config=./pyproject.toml] language_version: python3.11 - repo: https://github.com/pycqa/flake8 rev: 6.0.0 hooks: - id: flake8 args: [--config=./tox.ini] language_version: python3.11 - repo: https://github.com/pycqa/isort rev: 5.12.0 hooks: - id: isort args: ["--profile", "black", "--filter-files"] language_version: python3.11 - repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.4.0 hooks: - id: requirements-txt-fixer language_version: python3.11 - id: debug-statements - id: detect-aws-credentials - id: detect-private-key
- Automate Python Linting and Code Style Enforcement with Ruff and GitHub Actions
-
Improve your Django Code with pre-commit
repos: ... pre-commmit stuff ... black stuff - repo: https://github.com/pycqa/isort rev: 5.12.0 hooks: - id: isort name: isort (python)
-
How I start every new Python backend API project
isort
-
nbdev formating and linting
isort , A Python utility / library to sort imports.
-
Curious what is too much on one line... how 'compressed' can our code be?
Install black and isort and just don't worry about it. :-)
-
I wrote a script to periodically change my Desktop background to live satellite images!
Sure. Also, and don't take this the wrong way, but there are some code smells in your project that could be partially mitigated with some basic linting/formatting. I suggest black as a code formatter, flake8 for basic linting, and isort for sorting imports (for example, you have local imports mixed in with standard library and third party imports). You can install these via pip and most editors (like VS Code) can autoformat on save and show you linting problems as you edit. And you can integrate these into your workflow by using pre-commit.
What are some alternatives?
autopep8 - A tool that automatically formats Python code to conform to the PEP 8 style guide.
prettier - Prettier is an opinionated code formatter.
yapf - A formatter for Python files
Pylint - It's not just a linter that annoys you!
ruff - An extremely fast Python linter and code formatter, written in Rust.
autoflake - Removes unused imports and unused variables as reported by pyflakes
Flake8 - flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
pycodestyle - Simple Python style checker in one Python file
mypy - Optional static typing for Python
google-java-format - Reformats Java source code to comply with Google Java Style.