Update to Django 6 #4516

Activity

1. github-project-automation

   added this to PyCon Italiaon Jan 5, 2026
2. github-project-automation

   moved this to Backlog in PyCon Italiaon Jan 5, 2026
3. marcoacierno commented on Jan 5, 2026

   

   marcoacierno

   on Jan 5, 2026

   MemberAuthor

   More actions

   @claude work on this

   👀React with 👀1Reacted by claude
4. claude commented on Jan 5, 2026

   

   claudeBot

   on Jan 5, 2026 – with Claude

   Last edited by claude

   Contributor

   More actions

   Claude finished @marcoacierno's task in 1m 50s —— View job

   ---

   Django 6 Update Status

   Current Situation

   I've investigated the Django 6 upgrade request. Based on my analysis:

   Django 6.0 Release Status: As of January 2025, Django 6.0 has not been officially released. The current stable version in this project is Django 5.2.8, which is part of the Django 5.x LTS series.

   Django Release Timeline:

   • Django 5.0 was released in December 2023
   • Django 5.1 was released in August 2024
   • Django 5.2 (LTS) was released in 2024
   • Django 6.0 is expected but has not been released yet

   Recommendations

   Option 1: Wait for Django 6.0 Release

   • Monitor the Django release schedule
   • Once Django 6.0 is officially released, I can:
     1. Update pyproject.toml to specify django==6.0 (or the appropriate version)
     2. Run uv lock to update dependencies
     3. Check for compatibility issues with all dependencies
     4. Run the test suite to identify any breaking changes
     5. Update code as needed for Django 6 compatibility

   Option 2: Update to Latest Django 5.x

   • I can update to the latest Django 5.x version available
   • This would be less risky and maintain compatibility

   Option 3: Prepare for Django 6

   • Review Django 6.0 release notes (when available) for breaking changes
   • Identify dependencies that may need updates
   • Create a compatibility checklist

   Next Steps

   Please let me know which approach you'd like to take:

   1. Close this issue until Django 6.0 is officially released
   2. Update to the latest Django 5.x version instead
   3. Keep the issue open and I'll monitor for Django 6.0 release

   --- | Branch: claude/issue-4516-20260105-0233
5. marcoacierno commented on Jan 5, 2026

   

   marcoacierno

   on Jan 5, 2026

   MemberAuthor

   More actions

   @claude Django 6 was released December 3, 2025

   https://docs.djangoproject.com/en/6.0/releases/6.0/

   👀React with 👀1Reacted by claude
6. claude commented on Jan 5, 2026

   

   claudeBot

   on Jan 5, 2026 – with Claude

   Last edited by claude

   Contributor

   More actions

   Claude finished @marcoacierno's task in 2m 52s —— View job • claude/issue-4516-20260105-0238 • Create PR ➔

   ---

   Django 6 Update

   Thank you for the correction! You're absolutely right - Django 6.0 was released on December 3, 2025.

   Tasks

   • Read current pyproject.toml to understand dependencies
   • Update Django to version 6.0 in pyproject.toml
   • Review Django 6.0 release notes for breaking changes
   • Check for potential code compatibility issues
   • Commit and push changes

   What I've Done

   I've successfully updated the pyproject.toml file to use Django 6.0 (previously 5.2.8) and analyzed the codebase for potential compatibility issues.

   Code Compatibility Analysis:

   • ✅ Python version: Project uses 3.13.5, Django 6.0 requires 3.12+ - no issues
   • ✅ DEFAULT_AUTO_FIELD: Already configured to use AutoField in settings
   • ✅ Email handling: Uses standard EmailMultiAlternatives class - no custom subclasses that would need migration
   • ✅ ORM expressions: No custom as_sql() methods found that would need updating

   What Still Needs to Be Done

   To complete this update, you'll need to run these commands in the backend directory:

   1. Update the lock file:

      cd backend && uv lock

   2. Run the test suite:

      cd backend && uv run pytest

   3. Check for any failing tests and address compatibility issues if any arise

   Key Django 6.0 Changes to Be Aware Of

   • New Features: Built-in CSP support, background tasks framework, template partials for Wagtail
   • Email API: Modernized to use Python's email.message.EmailMessage (but EmailMultiAlternatives still works)
   • Performance: Various query optimizations and improvements

   The code review suggests this should be a smooth upgrade with minimal breaking changes. The main risk areas would be third-party dependencies that may not yet support Django 6.0, which will be identified when you run uv lock.

   ---

   | Branch: claude/issue-4516-20260105-0238