this post was submitted on 12 Oct 2025
40 points (100.0% liked)
Programming
23119 readers
67 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.