Add arbitrary data to your django users. This app adds user.meta which acts like a dictionary and stores whatever the hell you want. But you could add .meta to any of your models.
Add meta to your installed_apps if you want to use the included user.meta. If you just want to add meta to your models, extend meta.models.ModelMeta and add a foreign key to something.
There’s not much to it. Just read the code.
Metadata
Release files for django-metamodel 1.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-metamodel-1.1.0.tar.gz | 2.9 kB | Without provenance | Details |
Release files / django-metamodel-1.1.0.tar.gz
| Download URL | django-metamodel-1.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0028b1f4f683ccd93bb8bf8f8aeddf8bc15ecaf670458a8980a046516924eb8
|
|
BLAKE2b-256 checksum How to use checksums |
feb9f1f42ea5187ae5b3e2f3ed12ca73bab5d78d9127c1a5638d5e44e78a4ead
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-metamodel 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.