Django-Binder
Code Yellow backend framework for SPA webapps with REST-like API.
Running the tests
- Run with
./test - Access the test database directly by with
docker compose run --rm db psql -h db -U postgres. - It may be possible to recreate the test database (for example when you added/changed models). One way of achieving this is to just remove all the docker images that were build
docker compose rmordocker compose down db binder. The database will be created during the setup intests/__init__.py.
The tests are set up in such a way that there is no need to keep migration files. The setup procedure in tests/__init__.py handles the preparation of the database by directly calling some build-in Django commands.
To only run a selection of the tests, use the -k flag like ./test -k tests.test_some_specific_test.
MySQL support
MySQL is supported, but only with the goal to replace it with PostgreSQL. This means it has a few limitations:
wherefiltering onwithrelations is not supported.- Only integer primary keys are supported.
- When fetching large number of records using
withor the ids are big, be sure to increaseGROUP_CONCATmax string length by:
DATABASES = {
'default': {
'OPTIONS': {
'init_command': 'SET SESSION group_concat_max_len = 1000000',
},
},
}
Metadata
Release files for django-binder 2.0.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 | Actions |
|---|---|---|---|---|
| django_binder-2.0.0.tar.gz | 141.0 kB | Without provenance | Details for django_binder-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_binder-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for django_binder-2.0.0-py3-none-any.whl |
Total release size: 320.4 kB
Release files / django_binder-2.0.0.tar.gz
| Download URL | django_binder-2.0.0.tar.gz |
|---|---|
| Size | 141.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a9d71fb1a301321d0c4b12595e07206308fa45459adb3b957e650ee91c9467f
|
|
BLAKE2b-256 checksum How to use checksums |
67f61d56732bd83214a0a5ca471f6c024e072b4290c107853d22314e6c017838
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / django_binder-2.0.0-py3-none-any.whl
| Download URL | django_binder-2.0.0-py3-none-any.whl |
|---|---|
| Size | 179.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23b009cf9b0b792c5b9946b2ab5bfd72cbc2e2c15739325f45474170c975c17f
|
|
BLAKE2b-256 checksum How to use checksums |
39f76d5f958c28c6e9052b6e2ab043edfbac34467b54943525452f631d0cadd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for django-binder 2.0.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.