This release is a pre-release and may not be stable for production use.
django-mz-users
The user model and user management for Django projects of the django-mz family (projects whose admin drives an API and a Vue frontend). It is a small, plain Django app that any project can use.
Status: alpha (0.1.0a1). The API may change before 1.0.
Why a custom user model from the start
Django recommends a custom user model for every new project: switching AUTH_USER_MODEL later, on a live
database, is hard. mz_users.User is Django's standard user (AbstractUser) in its own app, so projects can share
it and extend it later without that switch.
Installation
pip install django-mz-users
INSTALLED_APPS = [..., 'django.contrib.auth', 'mz_users', ...]
AUTH_USER_MODEL = 'mz_users.User'
Set it before the first migrate of the project. The app label is mz_users (table mz_users_user).
What is included
mz_users.User– the user model (AbstractUser), Czech labels included- admin registration with Django's
UserAdmin: the new-user form asks for the password twice
Planned: self-registration, password reset by e-mail and other user management, as API views for the frontend.
Development
uv run --package django-mz-users pytest
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for django-mz-users 0.1.0a1
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 | Actions |
|---|---|---|---|---|
| django_mz_users-0.1.0a1.tar.gz | 4.3 kB | Without provenance | Details for django_mz_users-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_mz_users-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for django_mz_users-0.1.0a1-py3-none-any.whl |
Total release size: 11.5 kB
Release files / django_mz_users-0.1.0a1.tar.gz
| Download URL | django_mz_users-0.1.0a1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c664270f9b2462524c571c59c0f85e9138bb49aeded41991b56d42aa8d7b3a03
|
|
BLAKE2b-256 checksum How to use checksums |
909911bfa84941d226a70a57f15d0331dbbfb5f78835518ee0460594690a7c36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":null,"id":"forky","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / django_mz_users-0.1.0a1-py3-none-any.whl
| Download URL | django_mz_users-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b10d7dd7042efd8f90fd4718d5b1bb785c3e2412f14a8575318bf7faf9d5f750
|
|
BLAKE2b-256 checksum How to use checksums |
5df27eac342de66eb5c94d18822895f3b5d0073f35c7cb9a8993919990df9361
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":null,"id":"forky","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for django-mz-users 0.1.0a1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
