This release is a pre-release and may not be stable for production use.
Django Accu
More batteries for Django - an opinionated package for creating a Django application faster.
Architecture
This project is not flexible in the supported architecture, it makes clear assumptions about the used structure. It uses:
- Python >=3.9
- Django >=4.1
- DRF => 3.14
- Django Q => 1.3
- Sentry (optional)
Provided namespaces:
Currently available
- https://github.com/matmair/django-accu/issues/1 core.checks: checks to make sure the Django project confirms to core assumptions made
- https://github.com/matmair/django-accu/issues/2 core.config: utils to load settings from different sources (environment, .env, config files, ...)
- https://github.com/matmair/django-accu/issues/3 core.clean: clean user inputs with bleach
- https://github.com/matmair/django-accu/issues/4 core.urls: import for this project URLs
- https://github.com/matmair/django-accu/issues/5 core.utils: helper functions
- https://github.com/matmair/django-accu/issues/6 tasks: async execution of functions
On the roadmap
- https://github.com/matmair/django-accu/issues/7 plugins: a plugin implementation for Django
- https://github.com/matmair/django-accu/issues/8 settings: database settings
- https://github.com/matmair/django-accu/issues/8 settings.api: expose the settings for consumption in apps/frontends
TODO/to be ported from codebases
- users: expandable user (uses a profile to expand the model to keep usability with other projects high)
- changelogs
- approvals
- setups
- core.update
- reports.client (jasper-server-based)
- reports.file (jasper-file-based
To be finished and ported:
- users.token: multi-token implementation for usage with DRF
- core.security.api: expose all core security flows via API (registration, login, logoff, deletion, MFA-actions, password-reset)
WARNING
THIS IS CURRENTLY A PLACEHOLDER WHILE SOME HURDLES ARE CLEARED
Acknowledgement
This repo contains code from InvenTree/InvenTree (MIT licensed), MissionLog (closed source, with permission) and several closed source projects I (matmair / mjmair.com) work on with the permission of the owners.
Metadata
Release files for accu 0.1a2
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 |
|---|---|---|---|---|
| accu-0.1a2.tar.gz | 12.2 kB | Without provenance | Details for accu-0.1a2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| accu-0.1a2-py3-none-any.whl | Python 3 | none | any | Details for accu-0.1a2-py3-none-any.whl |
Total release size: 28.7 kB
Release files / accu-0.1a2.tar.gz
| Download URL | accu-0.1a2.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b20fe8850d474d8330731dce6d478ab7eb819eb0166c0bacf5669330583e78e3
|
|
BLAKE2b-256 checksum How to use checksums |
b85cfc1324d05fd397f5a543b82649c46ca7c91aef67747891070b81046f6c77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Release files / accu-0.1a2-py3-none-any.whl
| Download URL | accu-0.1a2-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ba2a62183275ed92da0761f5a5d3e3c10864bfa844047d899c314f2a0635c91
|
|
BLAKE2b-256 checksum How to use checksums |
fbf6b2503e33c898c5cdaefcea75772d050c65204f0d9f72b74a6424844934ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Security for accu 0.1a2
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.