What we do
Tools
Industries
Department
How we workLet's talk →
Home/Django Developer for Hire
Django Development

Django Developer for Hire, Starting With the Version You Run

Django's admin, ORM and auth are why the app got built quickly. They're also why it keeps running long after anyone checks it: no patch reminders, no alarms when a release stops getting security fixes. Look up your version in requirements.txt or pyproject.toml, then find it below.

Is your Django version still getting security fixes?

From the Django project's own download page. Security fixes stop on the end date, and an app past it collects known holes with no patch coming.

Your Django version Where it stands now Next step
4.2 LTS or anything older (3.2, 2.2, 1.x) Unsupported. 4.2 was the last of these to get fixes. Upgrade to 5.2 LTS, one feature release at a time. The Python version on the server will usually need to move too.
5.2 LTS Supported, with security fixes until April 2028. Stay current on 5.2 patch releases, and clear deprecation warnings so the jump to the next LTS is small.
6.0 Security fixes only, until April 2027. Plan a move to 6.1 or to the 6.2 LTS due in April 2027, before the window closes.
6.1 Current release, supported until December 2027. Fine for now. If you'd rather upgrade less often, aim for the next LTS instead of every release.

Upgrading an old Django app without breaking it

Django's own upgrade notes recommend going through each feature release in turn. That's slower on paper and faster in practice.

  1. 1

    Pin everything and get it running locally

    Freeze the exact package versions the live server runs, and get a copy working on a developer's machine with a copy of real data. Until that works, nothing else is safe.

  2. 2

    Write a few tests around what staff do every day

    Logging in, the admin screens people use, the reports, anything that takes money. A dozen tests is enough to tell whether an upgrade broke something.

  3. 3

    Run with deprecation warnings on

    Run the tests with python -Wa manage.py test. Every warning is something the next version removes. Fix them on the current version before upgrading.

  4. 4

    Step one feature release at a time

    Read that release's notes, bump Django, update the packages that need it, fix what fails, and deploy. Then the next one. Third-party apps that were abandoned get replaced or folded into the project.

    Watch for: Python itself. Each Django release supports a range of Python versions, so the server's Python often has to move in the middle of the path.

  5. 5

    Run the deploy check

    python manage.py check --deploy flags settings that are unsafe in production, like DEBUG left on or missing secure cookie settings. Old apps often fail a few.

When Celery tasks go missing in a Django app

Celery handles the work Django hands off: emails, imports, invoices, calls to other systems. Its failures are quiet, so they usually reach you as a customer complaint.

The task ran before the record existed

How you'll know: A task fails with "DoesNotExist" now and then, for an order or user that's clearly in the database when you look.

Fix: The task was queued inside a database transaction and a worker picked it up before the commit. Queue it with transaction.on_commit so it only goes out once the data is saved.

Scheduled jobs fire twice

How you'll know: Nightly emails or reports go out in pairs, often since the app moved to more than one server.

Fix: Celery beat was started on every server. Only one beat scheduler should run, so move it to a single process.

Tasks act on stale data

How you'll know: A task updates a record with values from before a staff member's edit, and their change disappears.

Fix: Pass the record's ID to the task, not the model object, and load it fresh inside the task.

Nobody sees the failures

How you'll know: Errors only show up in worker logs on the server, and nobody reads those.

Fix: Send task errors to the same error tracker as the web app, and alert when a queue stops emptying.

The Django admin your staff live in

In many businesses the Django admin quietly became the back office. It was fine with a few thousand rows and now takes ten seconds a page. That's rarely the framework. A list page that shows a related field without list_select_related runs one query per row. A dropdown listing every customer loads them all; autocomplete_fields or raw_id_fields fix that. On very large tables, show_full_result_count = False skips the slow count at the top of the page.

n-frames takes over Django apps that run the business: we bring them onto a supported release, fix the admin and the queries behind it, and make the Celery side reliable. If the work is mostly APIs other systems call, see API developer. For Python that isn't Django, see Python developer, and for heavy reporting queries, database developer and backend developer.

Let's talk

A Django app on a supported release, with an admin that keeps up

We start from your requirements file and a copy of the data, work out the upgrade path to a supported LTS, and quote that alongside whatever you actually need built. The admin speed-ups and Celery fixes usually come out of the same first pass.

Map the path to 5.2 LTS →

Questions people ask

Is this different from hiring a general Python developer?

Yes. A Django developer knows the admin, the ORM, migrations and the upgrade path between releases, which is most of the work on an existing app. For new work that doesn't need a web app with users and an admin, a general Python developer may fit better.

Can you take over a Django app that's behind on updates?

Yes. We get it running locally first, check its version against Django's supported releases, and lay out the upgrade path before recommending anything else.

Does Django still make sense for a growing app?

Usually. Large sites run on it. What needs attention as an app grows is query performance, the admin on big tables, background tasks and staying on a supported version, not the choice of framework.

How long does a Django upgrade take?

It depends on how many releases you're jumping and how many abandoned packages the app depends on. Going from 4.2 to 5.2 with healthy packages is a much smaller job than coming from 2.2. We quote it after a first look at the code.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.