Upgrade to Django 5.0

[pauloxnet]

As wrote by @bmispelon in the website repository:

Ideally, we would also want to be running the same version of Django on both djangoproject.com and code.djangoproject.com (https://github.com/django/code.djangoproject.com).
That's because the two sites talk to the same database (Trac uses Django's user database for authentication), and that might break if for example a newer version of Django changes the user model.

django/djangoproject.com#1712 (comment)

[bmispelon]

This needs #219 to happen first (that PR is almost ready I think, I just need to work out the issues with PYTHONWARNINGS)

[pauloxnet]

This needs #219 to happen first (that PR is almost ready I think, I just need to work out the issues with PYTHONWARNINGS)

I saw that #221 has been merged, so I opened #222

[bmispelon]

Fixed with #222

[ulgens]

Is there a plan to continue this upgrade with 5.1?

[bmispelon]

Is there a plan to continue this upgrade with 5.1?

Absolutely! My rough plan was to give it a week or two to see if things would pop up, then proceed with the 5.1 upgrade.

If you'd like to help, opening a PR for both djangoproject.com and code.djangoproject.com would be appreciated. Also running the test suite with warnings on to see if we might get bitten y some changes.

Thanks! 🎸