django-monkey-patches
| A collection of monkey patches to improve Django framework |
Use
Each monkey-patch beautiful_patch should be available
with a function apply_beautiful_patch().
Hence, all you have to do is:
from django_monkey_patches.django__beautiful_class__beautiful_patch\
import apply_beautiful_patch
apply_beautiful_patch()
For example, you can do it in your Django settings.py file or in a file imported in settings.py.
Choosing a patch
Look at the source code on GitHub. The rational behind each patch is given in the source code file. If you cannot bother reading the source code of a patch of ten or twenty lines, you probably should not apply it anyway ;).
F.A.Q.
Why does the version not follow Django versions?
Because I plan to add monkey-patches for other packages around Django itself. For example, Django Rest Framework (DRF) is in "maintenance mode only". It does not accept new features and is only updated to keep compatibility with new versions of Django. Moreover, many patches wil be plainly compatible with most versions of Django, and I don't see the need of multiplying versions. So instead, I use semantic versioning relative to the proposed patches.
Why is Django not a dependency?
See previous question.
Why is there no tests folder?
See previous question.
Metadata
Release files for django-monkey-patches 4.0.1
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_monkey_patches-4.0.1.tar.gz | 45.9 kB | Without provenance | Details for django_monkey_patches-4.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_monkey_patches-4.0.1-py3-none-any.whl | Python 3 | none | any | Details for django_monkey_patches-4.0.1-py3-none-any.whl |
Total release size: 97.2 kB
Release files / django_monkey_patches-4.0.1.tar.gz
| Download URL | django_monkey_patches-4.0.1.tar.gz |
|---|---|
| Size | 45.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55b2e801e4c42873d3a071a74b71938f909925243a081e3e806092e4e94e6d4d
|
|
BLAKE2b-256 checksum How to use checksums |
ce571571d494e37a1b1d8083ce42d0671bde3bffc12d5e32460d75adeb556e8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / django_monkey_patches-4.0.1-py3-none-any.whl
| Download URL | django_monkey_patches-4.0.1-py3-none-any.whl |
|---|---|
| Size | 51.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
744fa749c563b8b4b1bf7180fe90c16997d9435d8aa53c8786d54d2600640b4a
|
|
BLAKE2b-256 checksum How to use checksums |
ee0afa337bc3e8a08b8a310f8f289643b0c0555ad5dbf9c77b7b92ba180a08e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for django-monkey-patches 4.0.1
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.