Hotwired/Turbo django-allauth integration
This package provides subclasses modifying the django-allauth views https://github.com/pennersr/django-allauth to provide valid return codes.
This package is required in order to provide allauth compatability with Turbo. Turbo form validation either setting the attribute data-turbo="false" in the form, or returning a 4** response. This provides subclasses for the latter.
Disclaimer: the Hotwired/Turbo client libraries are, at time of writing, still in Beta. We expect there will be breaking changes until the first stable release. This package, and the Turbo client, should therefore be used with caution in a production environment. The version used in testing is @hotwired/turbo==7.0.0-beta.5.
Requirements
This library is tested for Python 3.8+ and Django 3.0+.
Installation
pip install django-turbo-allauth
To install from Git:
git clone https://github.com/hotwire-django/django-turbo-allauth
cd django-turbo-allauth
python setup.py install
Note: This library does not include any client libraries (Turbo or Stimulus). You may wish to add these yourself using your preferred Javascript build tool, or use a CDN. Please refer to the Hotwire documentation on installing these libraries.
Full documentation on ReadTheDocs:
https://django-turbo-allauth.readthedocs.io/en/latest/
License
This project is covered by the MIT license.
Changelog
Latest
Add support for Django 3.2
[0.0.7] - 2021-4-4
Removing support for Python 3.7
[0.0.6] - 2021-4-2
Dependency updates
[0.0.5] - 2021-2-4
Leverage turbo-response adapter mixin
[0.0.4] - 2021-2-2
Support for Python 3.7 and Django 3.0
[0.0.3] - 2021-7-1
Ensure redirects return a 303 in line with Turbo docs
[0.0.2] - 2021-5-1
Update to latest django-turbo-response, remove template partials
Metadata
Release files for django-turbo-allauth 0.0.10
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-turbo-allauth-0.0.10.tar.gz | 4.1 kB | Without provenance | Details for django-turbo-allauth-0.0.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_turbo_allauth-0.0.10-py3-none-any.whl | Python 3 | none | any | Details for django_turbo_allauth-0.0.10-py3-none-any.whl |
Total release size: 9.0 kB
Release files / django-turbo-allauth-0.0.10.tar.gz
| Download URL | django-turbo-allauth-0.0.10.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6506424b5c068f8b5753e6a288e5c0bc0defef01a45a5cf9372aa401560ca1e7
|
|
BLAKE2b-256 checksum How to use checksums |
6e43332866dd932141ae5603db899af38d98c2f9d6fdf5ed0ff7182501b2f549
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Release files / django_turbo_allauth-0.0.10-py3-none-any.whl
| Download URL | django_turbo_allauth-0.0.10-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6a151fd9b5ba67aa5b309cc7e4f2d1982a328e1e43f645f3dff8c73f5710f03
|
|
BLAKE2b-256 checksum How to use checksums |
990ce09d1385d5ccd9036585c9a866f15b4183d86543b67809492f4d6126211d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Security for django-turbo-allauth 0.0.10
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.