sourcery VS pyupgrade

In my experience, the developer tools that really catch on do so via word of mouth. For example, our whole team recently adopted https://sourcery.ai/ (not an ad) because one developer tried it and hyped it up to everyone else who also liked it.

To those that wish to automate a subset of these conventions, there is a tool called Sourcery[1] that I, personally, am a huge fan of! Not only does it have a large set of default rules[2], but it can also allow you to write your own rules that may be specific to your team or organization, and as mentioned it can enable you to follow Google's Python style guide as well[3].

There are some refactorings that Sourcery suggest that I don't agree with myself, namely the usage of 'contextlib.suppress'[4] as I don't like to introduce an additional 'import' statement just to do something so trivial. I wish Sourcery would add the relevance of having possibly too many 'import' statements as a heuristic.

---

[1]: https://sourcery.ai/

[2]: https://docs.sourcery.ai/Reference/Default-Rules/ (expand the sub-pages)

[3]: https://docs.sourcery.ai/Reference/Optional-Rules/gpsg/

During development, tools like Sourcery could show you improvements for code quality.

One of the first tools I install when setting up my Python dev environment is Sourcery. This still uses AI/ML to suggest code improvements to your Python code, but unlike GitHub's Copilot, it won't write code for you.

"Sourcery" exists

Looks downright wicked https://sourcery.ai/

As a bit of trivia, https://sourcery.ai/ will replace

I guess you have to signup in their website sourcery.ai. I actually don't use sourcery, I don't know the details on how to get the token.

When I'm writing Python, one of my favorite tools is [Sourcery](https://sourcery.ai/). Are there any similar tools for Go? What else do you recommend?

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