We have a Python 2, Django 1.4.22 webapp, with no realistic way to port it to Python 3, so now the only viable option is a full rewrite. Which will take a lot of time.
Mostly fixing stuff, of which there is a lot after moving servers (from a Debian 8 host to a Debian 13 VM with Debian 8 Repos, and different mail servers).
And yeah, Python 2 + Django 1.4 has many vulns, and mitigating them is a whole project.
We have a Python 2, Django 1.4.22 webapp, with no realistic way to port it to Python 3, so now the only viable option is a full rewrite. Which will take a lot of time.
Are you still actively working on/developing on the project?
Skipping new developments can be fine. Moving slow or not at all can mean stability and predictability.
The biggest issue is missed security updates, if they exist, or a lack of identification and fixing of open security issues.
And, of course, developer convenience if the project is still being actively worked on.
Mostly fixing stuff, of which there is a lot after moving servers (from a Debian 8 host to a Debian 13 VM with Debian 8 Repos, and different mail servers).
And yeah, Python 2 + Django 1.4 has many vulns, and mitigating them is a whole project.