django-le-twitter
Twitter authentication that sucks.
Django-le-twitter provides almost nothing to let your users sign in with twitter: two class-based views.
Django-le-twitter is based on Django >= 1.3 and Tweepy.
The concept is simple: when a user successfully logs in using twitter (i.e. you get a valid OAuth token), django-le-twitter executes a method that you define. There is no model instance created, no login using contrib.auth, no nothing. You decide.
Installation
pip install django-le-twitter
There’s nothing to add to your INSTALLED_APPS. It just needs to be in your python path. You need to add your Twitter app credentials to your Django settings:
CONSUMER_KEY = 'your key' CONSUMER_SECRET = 'your secret'
Usage
Subclass the two views provided by django-le-twitter in one of your apps’ views. Actually, one of them doesn’t strictly need to be subclassed.
# app/views.py
from django.http import HttpResponse
from le_twitter import views
authorize = views.Authorize.as_view()
class Return(views.Return):
def handle_error(self, error_msg, exception=None):
return HttpResponse(error_msg)
def handle_success(self, auth):
# Now it's up to you!
return HttpResponse('It worked!')
return_ = Return.as_view()
handle_success() gives you a tweepy.OAuth object containing your user’s OAuth credentials. At this point you can:
Fetch information using the tweepy API
Create an auth.User instance and link it to a custom twitter profile
handle_success() just needs to return an HttpResponse.
After that, just hook your custom views in your app urlconf:
# app/urls.py
from django.conf.urls.defaults import patterns, url
from app.views import authorize, return_
urlpatterns = patterns(''
url(r'^oauth/authorize/$', authorize, name='oauth_authorize'),
url(r'^oauth/return/$', return_, name='oauth_return'),
)
Metadata
Release files for django-le-twitter 0.2
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-le-twitter-0.2.tar.gz | 3.9 kB | Without provenance | Details for django-le-twitter-0.2.tar.gz |
Release files / django-le-twitter-0.2.tar.gz
| Download URL | django-le-twitter-0.2.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
225e15202604984babcdc94bdf5f0abd445fd493641b83293c45092c7cfe47b2
|
|
BLAKE2b-256 checksum How to use checksums |
7d4b6ce4bd1f736b6c86c0354e648eee91ecfdb7c00d22bac1d75f4442f5eec7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-le-twitter 0.2
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.