Add Django 6 compatibility and modernise codebase

[voyc-jean]

Hello.

Django 5.1 deprecated the undocumented django.utils.itercompat module. Django 6.0 removed it entirely, which leads to this package breaking when imported.

@stephrdev / @codeinthehole Many components of this project are quite outdated at this point. Is there interest in getting things up to date? If so, would it be best to retain compatibility with EOL versions of Python and Django, or create a version 4.0 which only supports Django 5.2+ / Python 3.10+?

[stephrdev]

I could imagine having a new major release with support for only the last LTS of Django. No need to build a lot of compat code. Any help would be more than appreciated :) Feel free to udpate this PR introducing a new major release + required changes in testing/code. Thank you so much!

[voyc-jean]

I could imagine having a new major release with support for only the last LTS of Django. No need to build a lot of compat code. Any help would be more than appreciated :) Feel free to udpate this PR introducing a new major release + required changes in testing/code. Thank you so much!

Hi @stephrdev

I've made these changes. I also felt like Docker compose would be preferred at this stage to Vagrant, as it allows easy reloading of Django by binding the sandbox directory to the container as a volume. Let me know if you disagree with this change.

Other changes include

• Support for Python 3.10+
• Support for Django 5.2+
• Upgrade Poetry and dependencies to newer versions
• Make use of Poetry dependency groups
• Modernisation of Python code (3.10+ compatible)
• Added Django debug toolbar to sandbox for easy cache debugging
• Fixes various spelling errors / typos
• Removal of deprecated functionality
• Default to Redis as a cache backend in sandbox instead of Memcached

Tests are working in Github Actions on my repo and the sandbox seems to be fully functional.

Let me know if you have any questions.