Django4.0 compatibility

[aymaneMx]

What does this do?

• replace force_text with force_str
• replace smart_text with smart_str
• replace from django.conf.urls import url with from django.urls import re_path

closes: #206

[Real-Gecko]

Can someone please arrange this? Really need Django upgrade.

[jheld]

I will try to review & merge this weekend.

[BartKalkman]

I there any update on this. We need the new version.

[jheld]

Sorry can you please add django 4.0 support into the .github/workflows/build.yml as that's where tests are officially run from?

[aymaneMx]

@jheld sure

[jheld]

@aymaneMx apologies but there is a bit more work to do on the test runner in github. Can you add similar exclude lines to what 3.2 has? I'll approve the test run now so we can easily see the failures but will wait to merge until those are configured differently.

[jheld]

please see pypi for version 1.3.3a1. once we're happy with the stability, i'll cut the official release.

[jheld]

how's the feedback? are we safe to cut the official release?

[Real-Gecko]

I'm developing with Django 4 and Easy Audit since #213, haven't seen any errors so far. But thing to note I did not monitor Easy Audit closely too.

[mschoettle]

how's the feedback? are we safe to cut the official release?

I've been running Django 4.0.3 and 1.3.3a6 for a couple weeks now locally. It is working fine but it is not heavy use currently (new project). I submitted #226 to fix the default_app_config deprecation warning that I keep getting, would be nice to get that into the next release.

[jheld]

release 1.3.3b1 is now PyPI and includes the fix on PR #226

Happy to cut the official release with an approval on usage of that version.