RepoJournal
Django @django
126 wires and counting

$ follow Django

Keep up with Django in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-25
stories 8
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

DJANGO STRIPS HARDCODED PRIMARY KEYS AHEAD OF NON-INTEGER ID SUPPORT

By RepoJournal · Filed · About Django · Composed from the cited sources · methodology

timgraham
1 person shipped this
timgraham @timgraham 2 cited

Django is systematically removing assumptions that primary keys must be integers, clearing the path for databases like MongoDB that use object IDs.

The framework removed hardcoded Site primary keys across the codebase [1], including a critical fix to runtests.py that now dynamically sets SITE_ID based on the database backend [2]. For MongoDB testing, this switches from hardcoded integer 1 to ObjectId('000000000000000000000001'), unblocking real-world usage of non-integer primary keys. The team also purged integer pk assumptions from AdminCustomQuerysetTest [3], with the same treatment applied elsewhere [4]. This isn't just cleanup. These changes signal Django is preparing for a world where UUIDs, ObjectIds, and other non-integer identifiers are first-class citizens, not edge cases. The deprecation roadmap is being updated to reflect this shift [5], giving extension developers and application authors clear guidance on what's coming. Benchmark infrastructure continues to mature across platforms [6], ensuring performance regressions get caught early.

$ ls django/reviews/ # the step-back reads

the week in review Django drops PostgreSQL 15 and PostGIS 3.2 the month in review Django 6.1, four CVEs, and a parallel-test fix that kills flaky runs
Topics: Python Full archive → Weekly reviews →

Quick answers

What shipped in Django on May 25, 2026?
Django is systematically removing assumptions that primary keys must be integers, clearing the path for databases like MongoDB that use object IDs. In total, 5 commits and 3 pull requests landed.
Who contributed to Django on May 25, 2026?
1 developer shipped this update, including timgraham.
What were the notable Django updates?
Removed hardcoded Site pks, Removed hardcoded Site pks, and Removed integer pk assumption in AdminCustomQuerysetTest.
♥

$ log @django --recent

Django drops PostgreSQL 15 and PostGIS 3.2, patches an admin date_hierarchy 500 7 shipped GenericIPAddressField accepts ipaddress objects, djangoproject.com tests go multi-browser 27 shipped GeneratedField null check reverted, sponsorship pages rebuilt 17 shipped Django ASV adds ubuntu-latest results, DSF publishes August and September minutes 2 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Rails Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.