Update requirements, in particular Django 4.0

[jochenklar]

Rationale / Begründung

Django 4.0 is out, we need to upgrade eventually. We should use this to review all other entries in requirements.txt.

[MyPyDavid]

are you gonna use this tool https://github.com/adamchainz/django-upgrade? ;)

[afuetterer]

Yes, I will give it try. But thanks for pointing it out.

The author also points out https://django-codemod.readthedocs.io.
He says codemod is slower. But I think, this does need to be run once and not be part of the pre-commit hooks.

I will upgrade these with priority: django and drf.

Do you know, if all the other requirements are stil needed?
I pointed out the issue with jsonfield in #692.
Also there is still this open issue about mptt #368.

Some of the dependencies have not received updates in a long time, e.g. https://github.com/chibisov/drf-extensions.

I will research the dependencies and report in the corresponding PR.

[afuetterer]

Could we also broaden some of the version constraints?

For example
"Django~=3.2.20" will only allow Django >= 3.2.20 and < 3.3

I would suggest using this form instead
"Django~=3.2", allowing Django >= 3.2 and < 4.0

See: https://peps.python.org/pep-0440/#compatible-release

[afuetterer]

@MyPyDavid, you can assign this issue to me.

[jochenklar]

Thanks for picking this up. I would not use a tool though. I did the migration once for a different project and it was pretty easy. I would just run the tests and fix the problems.

Are there particular problems with mptt and jsonfield and 4.2?

[afuetterer]

I will test the tool just to get to know it. But yes, the way you propose with fixing breaking tests makes sense.

No, there are no problems so far to my knowledge.

It was just an observation, that there is still an open issue regarding mptt. What to do with it?