For when you want regular Django users but email as usernames.
This is a stock replacement for Django’s auth.User model that removes the username field in favor of a unique email field. Both the User model and the forms enforce lower cased email addresses to ensure uniqueness without surprises.
Inspired by the users module in pydanny’s original Django cookiecutter project template which I kept using and then editing to support email addresses.
Installing
Install and download with pip:
pip install django-email-users
Add to your installed apps in your settings.py file:
INSTALLED_APPS = [
...
'users',
]
Change your project’s configured user in your settings.py file:
AUTH_USER_MODEL = 'users.User'
Profit.
1 maintainer
Metadata
1 maintainer
Release files for django-email-users 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_email_users-2.1.0.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_email_users-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.6 kB
Release files / django_email_users-2.1.0.tar.gz
| Download URL | django_email_users-2.1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
096992cbc309d754c077ce01a09316ea9bc2040b136963adfa2ff1e87cf1bc36
|
|
BLAKE2b-256 checksum How to use checksums |
63b0c9ff6140511ef176e9d04609d829c6dcde21ae3ea9b8639c6518f23406c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Release files / django_email_users-2.1.0-py3-none-any.whl
| Download URL | django_email_users-2.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73f488ae75451344ac2a5388fe366879262671595236dda1ed66fdd8de5462c0
|
|
BLAKE2b-256 checksum How to use checksums |
0fe131c93461208853126383a5a9c6c9a63989881f8cc12ed049fbbcb947b88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Security for django-email-users 2.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
