Skip to content

Conversation

@mweinelt
Copy link

@mweinelt mweinelt commented Oct 23, 2023

The django-allauth package since 0.56¹ requires setting up its middleware in settings.

Note that a PR² for dj-rest-auth is open to solve the situation there as well and merging should probably wait until they publish a new release.

[1] https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#backwards-incompatible-changes-1
[2] iMerica/dj-rest-auth#561

The django-allauth package since 0.56¹ requires setting up its
middleware in settings.

The same issue² was fixed in dj-rest-auth 5.0.2.

[1] https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#backwards-incompatible-changes-1
[2] iMerica/dj-rest-auth#561
@mweinelt
Copy link
Author

The django-allauth package dropped support for Python 3.6 in 0.54.0 released in 2023/03.

https://github.com/tfranzel/drf-spectacular/actions/runs/6613694377/job/18824130191?pr=1090

Python 3.6 is not supported by django-allauth>=0.54.0, which is now
the below the minimum required version.
@tfranzel
Copy link
Owner

So generally I would be willing to drop py3.6 from testing, but that seems not the only problem here.

I was unable to quickly come up with a combination of django-allauth dj-rest-auth and drf-jwt that works over the whole test set.

@mweinelt
Copy link
Author

Yeah, I failed at that step, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants