pyupgrade
pre-commit
Our great sponsors
pyupgrade | pre-commit | |
---|---|---|
23 | 192 | |
3,326 | 12,049 | |
- | 2.7% | |
7.9 | 8.0 | |
18 days ago | 4 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.
pyupgrade
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
pyupgrade and flynt are examples of tools that modify your code base from earlier python versions into the newest python syntax, rewriting all string formats into f-strings and similar things.
-
Conversion from the f-string literals to format method in python
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
-
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/.
-
Reasons Python Sucks
That's a decade to make a 30 second change. Add something like https://github.com/asottile/pyupgrade to your pre-commit hooks and you won't even need 25 of those seconds.
-
Is there a way to convert python 2 to 3 without finding every single line and fix it?
There is also pyupgrade: https://github.com/asottile/pyupgrade
-
I've recently learned about better support for type-hinting. What other 'best practices' have been introduced in Python 3.10 or newer?
pyupgrade is a useful tool that can help you find some of these things.
-
Flake8 took down the gitlab repository in favor of github
and last a little plug or two -- because I do this all for free and despite millions benefiting I receive zero proportional benefit from the maintenance work I put in -- consider sponsoring or maybe check out pre-commit.ci which would have automatically fixed this problem for you a year and a half ago
-
Django upgrade services?
Running https://github.com/adamchainz/django-upgrade with https://github.com/asottile/pyupgrade recursively will give an idea about how much work is there on Django side. Still, there may have dependency on third party libraries (both django+python). Another thing to consider is which role Django performing here, serving APIs or html views. As good test coverage is already there, you are on lucky side.
-
It’s Time to Say Goodbye to These Obsolete Python Libraries
Such goodness here and even points to an interesting project I’d never heard of for automated “de-deprecation”
https://github.com/asottile/pyupgrade
-
Is there a linter which would suggest using elif rather than an else in an if clause?
I do would like to recommend pyupgrade. Just pip install as expected and then run pyupgrade --py310-plus to drag your code kicking and screaming into $CURRENT_YEAR. Or at least into whatever version you're using :)
pre-commit
-
How to setup Black and pre-commit in python for auto text-formatting on commit
Today we are going to look at how to setup Black (a python code formatter) and pre-commit (a package for handling git hooks in python) to automatically format you code on commit.
-
Implementing Quality Checks In Your Git Workflow With Hooks and pre-commit
# See https://pre-commit.com for more information # See https://pre-commit.com/hooks.html for more hooks repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v3.2.0 hooks: - id: trailing-whitespace - id: end-of-file-fixer - id: check-yaml - id: check-toml - id: check-added-large-files - repo: local hooks: - id: tox lint name: tox-validation entry: pdm run tox -e test,lint language: system files: ^src\/.+py$|pyproject.toml|^tests\/.+py$ types_or: [python, toml] pass_filenames: false - id: tox docs name: tox-docs language: system entry: pdm run tox -e docs types_or: [python, rst, toml] files: ^src\/.+py$|pyproject.toml|^docs\/ pass_filenames: false - repo: https://github.com/pdm-project/pdm rev: 2.10.4 # a PDM release exposing the hook hooks: - id: pdm-lock-check - repo: https://github.com/jumanjihouse/pre-commit-hooks rev: 3.0.0 hooks: - id: markdownlint
-
Embracing Modern Python for Web Development
Pre-commit hooks act as the first line of defense in maintaining code quality, seamlessly integrating with linters and code formatters. They automatically execute these tools each time a developer tries to commit code to the repository, ensuring the code adheres to the project's standards. If the hooks detect issues, the commit is paused until the issues are resolved, guaranteeing that only code meeting quality standards makes it into the repository.
- EmacsConf Live Now
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
Pre-commit Hooks: Pre-commit is a tool that can be set up to enforce coding rules and standards before you commit your changes to your code repository. This ensures that you can't even check in (commit) code that doesn't meet your standards. This allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks.
-
Things I just don't like about Git
Ah, fair enough!
On my team we use pre-commit[0] a lot. I guess I would define the history to be something like "has this commit ever been run through our pre-commit hooks?". If you rewrite history, you'll (usually) produce commits that have not been through pre-commit (and they've therefore dodged a lot of static checks that might catch code that wasn't working, at that point in time). That gives some manner of objectivity to the "history", although it does depend on each user having their pre-commit hooks activated in their local workspace.
[0]: https://pre-commit.com/
-
Django Code Formatting and Linting Made Easy: A Step-by-Step Pre-commit Hook Tutorial
Pre-commit is a framework for managing and maintaining multi-language pre-commit hooks. It supports hooks for various programming languages. Using this framework, you only have to specify a list of hooks you want to run before every commit, and pre-commit handles the installation and execution of those hooks despite your project’s primary language.
-
Git: fu** the history!
You can learn more here: pre-commit.com
-
[Tool Anouncement] github-distributed-owners - A tool for managing GitHub CODEOWNERS using OWNERS files distributed throughout your code base. Especially helpful for monorepos / multi-team repos
Note this includes support for pre-commit.
-
Packaging Python projects in 2023 from scratch
As a nice next step, you could also add mypy to check your type hints are consistent, and automate running all this via pre-commit hooks set up with… pre-commit.
What are some alternatives?
pre-commit-hooks - Some out-of-the-box hooks for pre-commit
husky - Git hooks made easy 🐶 woof!
flynt - A tool to automatically convert old string literal formatting to f-strings
gitleaks - Protect and discover secrets using Gitleaks 🔑
black - The uncompromising Python code formatter
ruff - An extremely fast Python linter and code formatter, written in Rust.
pep585-upgrade - Pre-commit hook for upgrading type hints
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
autoflake - Removes unused imports and unused variables as reported by pyflakes
Poetry - Python packaging and dependency management made easy
black - The uncompromising Python code formatter [Moved to: https://github.com/psf/black]
pre-commit-golang - Pre-commit hooks for Golang with support for monorepos, the ability to pass arguments and environment variables to all hooks, and the ability to invoke custom go tools.