django-graphql-auth is not compatible with Django 4.0 because it doesn't require the latest version of django-graphql-jwt about django-graphql-auth HOT 7 OPEN

+1 on this issue.

from django-graphql-auth.

This project seems to be deprecated you can move on to strawberry where both this project and the jwt project migrated, maintained and tested with django 3.2 - 4 .

from django-graphql-auth.

Any update here?

from django-graphql-auth.

This project seems to be deprecated you can move on to strawberry where both this project and the jwt project migrated, maintained and tested with django 3.2 - 4 .

what do you mean? what does strawberry and where?

from django-graphql-auth.

@qari

• I mean that it is no longer maintained, and also I have talked with @PedroBern and he said that he intends to make this repo read only soon.
• Strawberry is one of the alternatives to the dying graphene, We have put a lot of work to migrate this project to strawberry so I would suggest using Strawberry over ariadne or other alternatives, also if you are into typing it is for sure better.

from django-graphql-auth.

There has been an update tographene-python on pypi, which is finally compatible with Django 4.0.

Could this motivate Pedrobern or someone else to update this library, so that it will also become compatible with Django 4.0?
Or am I misunderstanding and it should already work with Django 4.0? If not, are there any other issues besides the version loosening of the django-graphql-jwt package requirement?

from django-graphql-auth.

+1

from django-graphql-auth.