django-upgrade VS django-cacheops

30% of Django developers upgrade every LTS release[1]. As Django 3.2 runs out of support in April this year[2], it's worth celebrating Adam Johnson's package django-upgrade (https://github.com/adamchainz/django-upgrade) which has a set of fixers to automatically update your Django code to the version of your choice.

Curious if anyone has used 2to3 (https://docs.python.org/3/library/2to3.html) for upgrading Python code and can share their experience with it? Would you recommend?

1. https://lp.jetbrains.com/django-developer-survey-2022/

Take a look at https://github.com/adamchainz/django-upgrade

I had easy and quick upgrade from 3.2 to 4.1 using django-upgrade package. Project was pretty big, and I didn’t expect to be that easy to migrate to 4.1.

Regarding the actual Django upgrade you might want to take a look at Django Upgrade https://github.com/adamchainz/django-upgrade - a tool to automate some of the boring tedious stuff in an upgrade.

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.

I recently upgraded one of my project to Django v4, from Django v1. The changes from Django 3 to 4 were fairly simple, just one line change in my case. The change log is extremely detailed, it was easy to upgrade. Also, I found a tool called django-upgrade which makes some changes automatically, rest I made manually.

Adam Johnson has written a nifty tool (https://github.com/adamchainz/django-upgrade) that can automatically do this for you. Even if you don't want to use the tool, the README generally outlines all the key issues you need to be aware of.

You should try the new [django-upgrade](https://github.com/adamchainz/django-upgrade) package. It claims you can either just run it or hook it into your CI. It will automatically take care of some of the heavy lifting for you.

Here is an example of such thing https://github.com/Suor/django-cacheops/blob/8b3a79de29b2545...

django-cacheops is a great package https://github.com/Suor/django-cacheops

Nuts, I was hoping that this was an evolution of https://github.com/Suor/django-cacheops which uses Redis to cache and invalidate ORM result sets by an abstracted representation of filter values. It works, but has a lot of magic (as is the Django way) and takes some tending-to in production.

i came across this and this i am failing to understand what is the difference between the two and which is better.

The solution I recommend is setting up the caching backend using like redis then bringing in this awesome project django-cacheops! Takes 5 minutes to set up (literally) and you’re done!

We use django cacheops with redis and its incredible!