Upgrade/django 3.0

[oleast]

What kind of a pull request is this?

• QA / Code Review

Code Checklist

• The code follows dotkom code style
• The code passes the defined tests
• I have added tests for the code I added
• I have provided documentation for the code I added
• The code is ready to be merged

(Possible) Breaking Changes

• The changes are backwards compatible

Description of changes

Upgrading Django to version 3, along with a lot of other dependencies to support it.
There are a few things that have been changed for Django support, but also a lot of tests that have been fixed because of changes in how Django Dynamic Fixtures creates model instances (new major version of the lib).

Screenshot(s) if appropriate

[henrikhorluck]

Great work so far!

I really think we should fix some of the deprecation warning you get when running make test-backend before merging, several thousand lines is not fun, I opened a PR to django-watson, that will fix some of it etianen/django-watson#270, eventually you can just use a git-dependency from my fork.

You forgot this ugettext

onlineweb4/apps/authentication/views.py

Line 15 in e1c8505

from django.utils.translation import ugettext as _

[oleast]

Great work so far!

I really think we should fix some of the deprecation warning you get when running make test-backend before merging, several thousand lines is not fun, I opened a PR to django-watson, that will fix some of it etianen/django-watson#270, eventually you can just use a git-dependency from my fork.

I've seen the deprecation warnings, and and they are quite annoying. The problem is that they are for Django 4, which is set to release in 2022. Some libs may not get to fixing those until close to that date.

[henrikhorluck]

As far as I can see on the deprecation warnings, the by far most common, and guilty for >10k of the lines was django-watson, which we have a potential fix for, and as long as that is fixed, and we remove django-oauth-toolkit, I think we should be relatively good

[henrikhorluck]

Great work! Would love if you also created an issue to clean up the warnings when running tests, because I think there ideally shouldn't be any 🙃