ModuleNotFoundError+No+module+named+social+django

Not specified by the original author.

ModuleNotFoundError: No module named 'social_django'

TL;DR: the distribution is called social-auth-app-django. Run pip install social-auth-app-django and the import works.

ModuleNotFoundError: No module named 'social_django'

The fix

pip install social-auth-app-django

Then add social_django to INSTALLED_APPS and include its URLs per the README.

Verify:

python -c "import social_django; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=social-auth-app-django+No+module+named+social_django'

When this applies

• Adding social login (Google, GitHub, etc.) to a Django project.
• Fresh virtualenvs, Docker builds, or CI runners.
• Migrating from the old monolithic python-social-auth package.

When it does NOT apply

• Backend or pipeline configuration errors after the import works.
• No module named 'social_core', which is the shared core package missing.

Why this happens

python-social-auth split into per-framework distributions (app-django, app-flask, and others) sharing social-auth-core. The distribution names describe the split; the module names kept the short forms. pip needs the long name, Python imports the short one.

Compatibility

social-auth-app-django 5.x with Django 4.x/5.x and social-auth-core 4.x. Installs the core automatically.

The module is social_django but the distribution is social-auth-app-django, part of the split python-social-auth ecosystem where each framework got its own distribution. The project README documents pip install social-auth-app-django as the install command. Django projects adding social login hit this constantly because the import name suggests nothing about the distribution name.

Not specified by the original author.

ModuleNotFoundError: No module named 'allauth'

TL;DR: the distribution is called django-allauth. Run pip install django-allauth and the import works.

ModuleNotFoundError: No module named 'allauth'

The fix

pip install django-allauth

Then follow the docs to add allauth apps to INSTALLED_APPS and wire the URLs.

Verify:

python -c "import allauth; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=django-allauth+No+module+named+allauth'

When this applies

• Adding social or email login to a Django project.
• Fresh virtualenvs, Docker builds, or CI runners.
• You ran pip install allauth and it did not help.

When it does NOT apply

• Provider configuration errors after the import works.
• No module named 'allauth.account', which can mean INSTALLED_APPS is misconfigured rather than the package missing.

Why this happens

Same distribution-name versus import-name split as the rest of the Django ecosystem: pip needs django-allauth, Python imports allauth. The docs' installation section is authoritative; the bare allauth name on PyPI is not this project.

Compatibility

django-allauth 65+ (0.6x line) with Django 4.x/5.x. The 65.x releases renamed some settings; check the changelog when upgrading across majors.

The module is allauth but the distribution is django-allauth, so pip install allauth grabs the wrong thing or fails. The django-allauth documentation's installation page gives pip install django-allauth as the command. Every Django project adding social login hits this the first time, since the import name gives no hint of the distribution name.

Not specified by the original author.

ModuleNotFoundError: No module named 'oauth2_provider'

TL;DR: the distribution is called django-oauth-toolkit. Run pip install django-oauth-toolkit and the import works.

ModuleNotFoundError: No module named 'oauth2_provider'

The fix

pip install django-oauth-toolkit

Then add oauth2_provider to INSTALLED_APPS and include its URLs per the README.

Verify:

python -c "import oauth2_provider; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=django-oauth-toolkit+No+module+named+oauth2_provider'

When this applies

• Turning a Django app into an OAuth2 provider (issuing tokens to third parties).
• Fresh virtualenvs, Docker builds, or CI runners.
• Confusing this with oauth client libraries like authlib or requests-oauthlib.

When it does NOT apply

• OAuth2 client-side code, where authlib or requests-oauthlib is the right package.
• Token or scope configuration errors after the import works.

Why this happens

The distribution name describes the Django toolkit; the module name describes the OAuth2 provider app inside it. pip needs the long name, Python imports the short one. This is the same split as djangorestframework-simplejwt and django-allauth.

Compatibility

django-oauth-toolkit 2.x/3.x with Django 4.x/5.x. Version 2.0+ dropped older Django; check the changelog when upgrading.

The module is oauth2_provider but the distribution is django-oauth-toolkit, so the pip name guess from the import fails. The django-oauth-toolkit README documents pip install django-oauth-toolkit as the install command. Django projects adding an OAuth2 provider (not just a client) hit this the first time, since nothing about oauth2_provider suggests the toolkit name.