codespell VS pyupgrade

You probably should use a separate linter for this. I use codespell in Neovim. You can use it from CLI and it is not Python specific.

This plus codespell. Because we’d look like kindergartners otherwise.

I keep making silly tyops like that, so I always add codespell as one of the pre-commit hooks of all the repositories I own.

codespell

codespell checks for typos. We chose this tool because it is based on a list of common typos, which reduces the number of false positives to a minimum.

Something like https://github.com/codespell-project/codespell

--- # .pre-commit-config.yaml # ======================== # # pre-commit clean # pre-commit install # pre-commit install-hooks # # precommit hooks installation # # - pre-commit autoupdate # # - pre-commit run black # # continuous integration # ====================== # # - pre-commit run --all-files # repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.0.1 hooks: - id: trailing-whitespace - id: end-of-file-fixer - id: debug-statements - id: check-merge-conflict - id: sort-simple-yaml - id: fix-encoding-pragma args: ["--remove"] - id: forbid-new-submodules - id: mixed-line-ending args: ["--fix=lf"] description: Forces to replace line ending by the UNIX 'lf' character. - id: check-added-large-files args: ["--maxkb=500"] - id: no-commit-to-branch args: [--branch, master] - id: check-yaml - id: check-json files: ^tests/app/ - id: pretty-format-json args: ["--no-sort-keys", "--autofix"] files: ^tests/app/ - repo: meta hooks: - id: check-hooks-apply - id: check-useless-excludes - repo: https://github.com/ambv/black rev: 21.5b1 hooks: - id: black language_version: python3.9 - repo: https://github.com/PyCQA/bandit rev: 1.7.0 hooks: - id: bandit description: Security oriented static analyser for python code exclude: tests/|scripts/ args: - -s - B101 - repo: https://github.com/codespell-project/codespell rev: v2.1.0 hooks: - id: codespell name: codespell description: Checks for common misspellings in text files. entry: codespell language: python types: [text] - repo: https://github.com/asottile/pyupgrade rev: v2.19.4 hooks: - id: pyupgrade

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.

pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.

He made yesqa and pyupgrade (among others), and also works on flake8. His main job is for https://sentry.io/.

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.

There is also pyupgrade: https://github.com/asottile/pyupgrade

pyupgrade is a useful tool that can help you find some of these things.

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

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.

Such goodness here and even points to an interesting project I’d never heard of for automated “de-deprecation”

https://github.com/asottile/pyupgrade

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 :)