Bootstrap 4 forms for Django
Bootstrap 4 integration for django using widget templates that were introduced in Django 1.11.
Motivation
This library is meant to be a drop-in replacement for django-bootstrap4. See below for a list of differences. I really like that library, but it is hard to customize some things because everything is done in python functions. By using widget templates, I hope this library is more flexible.
Installation
Install with pip:
pip install django-bs4
After that you have to add it to INSTALLED_APPS. You also need to make sure that the correct FORM_RENDERER is selected and django.forms is in INSTALLED_APPS (after django-bs4). This is required so that widget templates can be overwritten:
INSTALLED_APPS = [
…
'django-bs4',
…
'django.forms',
…
]
FORM_RENDERER = 'django.forms.renderers.TemplatesSetting'
Usage
The following template tags are included in the bootstrap4 library:
bootstrap_field {boundfield} - Render a single field.
bootstrap_form {form} - Render errors and all fields for a form. The <form> element itself is not included.
bootstrap_messages - Render messages from django.contrib.messages.
bootstrap_pagination {page} - Render pagination. A <nav> element is not included.
Please refer to the source code for additional parameters.
Differences to django-bootstrap4
Uses widget templates instead of custom renderers. IMHO this makes the code much easier to read and customize. A big downside is that I had to monkey-patch BoundField.as_widget() to include some information that would otherwise not be available in the widget templates.
Concentrates on forms fields and does therefore not include some others features.
Uses small.text-danger instead of .invalid-feedback as it does not depend on DOM location. (see also twbs/bootstrap#29439)
Does not use .is-valid because I find it confusing with server-side rendering.
Does not include dismiss-buttons for alerts to avoid depending on JavaScript.
Does not include field errors at the top of forms as they are already displayed on the fields themselves.
Improved ARIA support.
You will have to load bootstrap yourself.
No configuration.
Metadata
Release files for django-bs4 0.0.3
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-bs4-0.0.3.tar.gz | 6.6 kB | Without provenance | Details for django-bs4-0.0.3.tar.gz |
Release files / django-bs4-0.0.3.tar.gz
| Download URL | django-bs4-0.0.3.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a28742a2aa5c5ae1d67a3dc6c91df9ac1c1815d95f13e546da9b9aa33fb705c
|
|
BLAKE2b-256 checksum How to use checksums |
02ac147e256ed2fdf1d4c803fe83d3a6e0737b1bfe2cb9a1d0dda822ed84686b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.3
|
Security for django-bs4 0.0.3
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.