I wish to express my apologies, when I opened #152 I did not mean to open a pull request with the upstream project as I did and I probably created a lot of merge conflicts by getting mine accepted. I am however happy to merge efforts and stop maintaining a fork, but my fork has significant architectural changes that require migration efforts when upgrading.

I was trying to test/setup CI when I created #152 and the branch was only half baked when it was merged. I will have more updates soon that will actually resolve some of the django 4 incompatibilities. The latest changes that get python 3.0-4.1 working with python3.8 can be found here:
https://github.com/stormsherpa/django-oauth2-provider/tree/update_python38_django4