Django all-auth不兼容Django 2.01？求适配方法及新版本发布时间

Hey there! Let's tackle your two questions about django-all-auth and Django 2.0.1 step by step:

First off, you're right that the latest versions of django-all-auth no longer support Django 2.x—they've shifted focus to newer Django releases like 3.0 and above. But don't worry, there are older, fully compatible versions of django-all-auth that work seamlessly with Django 2.0.1. Here's how to get set up:

• Install a compatible version: Use pip to install a specific release that explicitly supports Django 2.0. Versions in the 0.40.x to 0.46.x range are verified to work well. For example:

  pip install django-allauth==0.40.0
  

  You can cross-check exact compatibility by reviewing the project's release notes (included in the repository's CHANGELOG) if you need a different patch version.

• Configure your Django project:

  1. Add required apps to INSTALLED_APPS in settings.py:

     INSTALLED_APPS = [
         # ... your existing project apps
         'django.contrib.sites',
         'allauth',
         'allauth.account',
         'allauth.socialaccount',
         # Add social providers you need, e.g., 'allauth.socialaccount.providers.github'
     ]
     

  2. Set the mandatory SITE_ID:

     SITE_ID = 1
     

  3. Update authentication backends to include all-auth:

     AUTHENTICATION_BACKENDS = [
         'django.contrib.auth.backends.ModelBackend',
         'allauth.account.auth_backends.AuthenticationBackend',
     ]
     

  4. Add all-auth URLs to your project's urls.py:

     from django.urls import path, include
     
     urlpatterns = [
         # ... your existing URLs
         path('accounts/', include('allauth.urls')),
     ]
     

• Run database migrations: Apply the necessary migrations for all-auth's models:

  python manage.py migrate
  

After these steps, you'll be able to use all core features of django-all-auth—like email/password authentication, social logins, and account management—with your Django 2.0.1 project.

django-all-auth doesn't follow a rigid, fixed release schedule. New versions are rolled out when maintainers have addressed critical bugs, added high-priority features, or updated compatibility with newer Django/Python versions. Generally, you can expect minor releases every 1-3 months, and major releases (with breaking changes) once or twice a year.

To stay informed about upcoming releases:

• Check the project's release history and CHANGELOG in its repository to spot past release patterns.
• Watch the repository to get real-time notifications when new versions are published.
• Participate in the project's issue discussions where maintainers sometimes share roadmap details.

内容的提问来源于stack exchange，提问作者Shohan