Skip to content

Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS ([Bug] #195)#229

Open
YaruG1022 wants to merge 12 commits into
taigaio:mainfrom
WSU-CptS-481-Spring-2026:issues/195/outdated-package-vulnerability
Open

Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS ([Bug] #195)#229
YaruG1022 wants to merge 12 commits into
taigaio:mainfrom
WSU-CptS-481-Spring-2026:issues/195/outdated-package-vulnerability

Conversation

@YaruG1022
Copy link
Copy Markdown

@YaruG1022 YaruG1022 commented Mar 8, 2026

Django 3.2 reached end-of-life in April 2024 and no longer receives security updates. This PR upgrades to Django 5.2 LTS and fixes all breaking changes encountered.

This change request addresses [Bug] #195

@YaruG1022 YaruG1022 changed the title Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS (#195) Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS (Bug #195) Mar 8, 2026
@YaruG1022 YaruG1022 changed the title Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS (Bug #195) Fix: migrate from Django 3.2 (EOL) to Django 5.2 LTS ([Bug] #195) Mar 8, 2026

from taiga.base.api import HTTP_HEADER_ENCODING

from email.message import Message as _Message
Copy link
Copy Markdown

@muellert muellert Mar 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the Django website, the fix should be to use django.utils.http.parse_header_parameters() instead. See https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous

One could also consider updating the PR to Django 6.0.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants