Refining pull requests regarding Django-4 compatibility

[raratiru]

... #101 #100 and #99 provide Django-4 support.

Which one is the winner?

[lnagel]

@raratiru Perhaps you could edit your issue title and description to be less aggressive in wording? This is after all a free software project that takes volunteer efforts to run.

The obvious question here is that are there any blockers that prevent releasing a Django 4 compatible version?

I can offer help to resolve any remaining issues if needed.

[raratiru]

Indeed, I apologize and I have changed the title.

I was about to start a pull request for this issue but there are already 3.

• Django 4 upgrade #101 seems to not cater of older versions but it certainly works on Django-4.0
• Fix ugettext and force_text import errors in Django 4.x #100 fixes the same issues as Django 4 upgrade #101 in a way that compatibility would be preserved
• add 4 support #99 applies the same fixes as Fix ugettext and force_text import errors in Django 4.x #100 along with changes in requirements.txt, urls.py in the example, refines setup.py and also bumps the version in __init__.py

I would vote for #99 .

[blueyed]

There is also #92.

[blueyed]

@marz619 are you planning to address pending PRs?

[raratiru]

@blueyed Yes! The winner is #92 !