Upgrade to Python 3.13 and Django 6

[delitamakanda]

Summary

• bump the stack to Python 3.13/Django 6 and refresh dependency versions to match
• modernize project settings for Django 6 (pathlib paths, timezone handling, whitenoise storage, updated CORS configuration)
• update URL routing to modern path/re_path usage and refresh documentation for the new runtime

Testing

• Not run (environment not yet configured for Python 3.13/Django 6 dependencies)

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace removed STATICFILES_STORAGE in Django 6

The settings now declare STATICFILES_STORAGE = 'whitenoise.storage.CompressedManifestStaticFilesStorage', but requirements pin the project to Django >=6.0a1. Django 6 removes the legacy STATICFILES_STORAGE/DEFAULT_FILE_STORAGE settings in favor of the STORAGES mapping, so keeping this line causes startup/staticfiles initialization to fail and prevents WhiteNoise from being used. Configure the STORAGES['staticfiles'] backend instead to keep the app running on the new Django version.

Useful? React with 👍 / 👎.

[delitamakanda]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved the merge conflicts in commit 5a3faee. The conflicts were in requirements.txt and requirements-dev.txt where master had incremental == version pins (Django 4.2.30, pandas 1.4.4, etc.) that conflicted with the PR's Django 6 >= constraints. Kept the PR's Django 6 versions since they supersede master's bumps. Also updated the CI workflow's Python version to 3.13 (master had bumped it to 3.10).

[delitamakanda]

@copilot downgrade django-embed-video to 1.4.10

[Copilot]

@copilot downgrade django-embed-video to 1.4.10

Done in commit 23fef1f — django-embed-video is now pinned to 1.4.10 in both requirements.txt and requirements-dev.txt.

[delitamakanda]

@copilot downgrade python3-memcached to 1.51

[Copilot]

@copilot downgrade python3-memcached to 1.51

Done in commit 331ae57 — python3-memcached is now pinned to 1.51 in both requirements.txt and requirements-dev.txt.

[delitamakanda]

@copilot
django-taggit-serializer not supported anymore what equivalent should you code ?

[Copilot]

@copilot
django-taggit-serializer not supported anymore what equivalent should you code ?

Done in commit f9cf2b9. Since django-taggit-serializer is abandoned and has no active replacement on PyPI, I implemented the equivalent directly in apps/common/serializers.py:

• TagListSerializerField – a DRF Field that serializes a TaggableManager as a flat list of tag name strings, and accepts both a list or a comma-separated string on write.
• TaggitSerializer – a mixin for ModelSerializer that auto-detects TagListSerializerField fields and calls TaggableManager.set(tags) after create/update.

Usage going forward:

from apps.common.serializers import TaggitSerializer, TagListSerializerField

class MySerializer(TaggitSerializer, serializers.ModelSerializer):
    tags = TagListSerializerField()
    ...

taggit_serializer has also been removed from INSTALLED_APPS and django-taggit-serializer dropped from both requirements files.