Features include:
Uses django.contrib.auth.User
Lets Twitter users sign in before registering.
Optional auto-creation of Users from Twitter screen-names
Lets Users link and unlink Twitter accounts.
Uses Django cache framework for caching results.
3 maintainers
Metadata
3 maintainers
Release files for django-oauth-twitter 1.11
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 | |
|---|---|---|---|---|
| django-oauth-twitter-1.11.tar.gz | 15.8 kB | Without provenance | Details |
Release files / django-oauth-twitter-1.11.tar.gz
| Download URL | django-oauth-twitter-1.11.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef9fa5a79f45c711fe3e63420fa67e3d95ab160aceb5f778d3b174d63954ec91
|
|
BLAKE2b-256 checksum How to use checksums |
993f68448951e64ebf0f4198f4f96780a900cdf33b8ea104b3a11b2f91f88c69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-oauth-twitter 1.11
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.
