Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ botocore>=1.39.15
celery>=5.5.3
coverage>=7.9.2
defusedxml>=0.7.1 # for TastyPie when using xml; not a declared dependency
Django>=4.2.30,<5
Django>=5.2.15

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

Upgrading Django to >=5.2.15 introduces several compatibility issues with the current project configuration and dependencies:

  1. Dependency Conflict: django-stubs is pinned to >=4.2.7,<5 (line 30), which is incompatible with Django 5.x. You will need to upgrade django-stubs to a version that supports Django 5.x.
  2. Removed Settings in ietf/settings.py:
    • USE_DEPRECATED_PYTZ (line 147) was completely removed in Django 5.0. This will cause a runtime configuration error. The project must be migrated to use standard zoneinfo instead of pytz.
    • USE_L10N (line 144) was also removed in Django 5.0.
  3. Form Renderers: DjangoDivFormRenderer (line 153) was a transitional class in Django 4.x and is no longer needed or supported in Django 5.x where div.html is the default.

These settings and dependencies must be updated in tandem with this Django upgrade to prevent build and runtime failures.

django-admin-rangefilter>=0.13.3
django-analytical>=3.2.0
django-bootstrap5>=25.1
Expand Down
Loading