Flake8-pyproject VS pyupgrade

I must try this some time https://pypi.org/project/Flake8-pyproject/ since the flake8 author refuses to add pyproject.toml support themselves. Marking the ticket as "too heated" and pull requests as spam, like he has something against the pyproject.toml format or something.

If you're sufficiently annoyed to accept an extra dependency over this (like I was), there's this: https://pypi.org/project/Flake8-pyproject/

Regarding setup.cfg, it's currently used for flake8 related configuration. Flake8 doesn't support pyproject.toml: https://github.com/PyCQA/flake8/issues/234. There are some workarounds, such as https://github.com/john-hen/Flake8-pyproject, but, in my opinion, getting rid of additional config file doesn't really justify additional dependency. However, as setup.cfg is currently used only for flake8 related configs, perhaps it could be replaced by .flake8 file.

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