Is your feature request related to a problem? Please describe.
The project currently utilizes Django 2.2 and various older packages that have known security vulnerabilities. This is a risk to the project as it may be exposed to potential security threats.
Describe the solution you'd like
The project dependencies should be updated to ensure the security impositions are resolved. Most importantly, Django should be upgraded from version 2.2 to version 3.2 and all other dependencies should be updated to their most recent stable versions.
Describe alternatives you've considered As an alternative,
we could consider replacing outdated packages with alternative packages if they impose less security vulnerabilities and do not disrupt the functionality of the project. Nonetheless, the best approach seems to be the update of all the project dependencies.
Additional context
The upgrade from Django 2.2 to Django 3.2 might require code changes since some features in Django 2.2 have been deprecated in Django 3.2. Additional changes may be required to adapt the project with the updated dependencies.
This feature request is deemed as necessary for the maintainability of the project.
Is your feature request related to a problem? Please describe. The project currently utilizes Django 2.2 and various older packages that have known security vulnerabilities. This is a risk to the project as it may be exposed to potential security threats.
Describe the solution you'd like The project dependencies should be updated to ensure the security impositions are resolved. Most importantly, Django should be upgraded from version 2.2 to version 3.2 and all other dependencies should be updated to their most recent stable versions.
Describe alternatives you've considered As an alternative, we could consider replacing outdated packages with alternative packages if they impose less security vulnerabilities and do not disrupt the functionality of the project. Nonetheless, the best approach seems to be the update of all the project dependencies.
Additional context The upgrade from Django 2.2 to Django 3.2 might require code changes since some features in Django 2.2 have been deprecated in Django 3.2. Additional changes may be required to adapt the project with the updated dependencies. This feature request is deemed as necessary for the maintainability of the project.