youtube-django


docs
tests
package

Install

$ pip install youtube-django

Add 'youtube_django' to your settings.

INSTALLED_APPS = [
    # [...]
    'youtube_django',
]

Run migrations:

$ python manage.py migrate

Add the following Google Oauth Settings to your settings.py:

GOOGLE_OAUTH2_CLIENT_ID = '<Your Client ID from Google Developer Console>'
GOOGLE_OAUTH2_CLIENT_SECRET = '<Your Client Secret from Google Developer Console>'
GOOGLE_OAUTH2_CALLBACK_VIEW = 'oauth2callback'  # your oauth callback view name

Add your views.Example:

from youtube_django.views import (
    VideoUploadView,
    AuthorizeView,
    Oauth2CallbackView,
)

urlpatterns = [
    path('^yt/upload/', VideoUploadView.as_view(), name='video_upload'),
    path('^yt/authorize/', AuthorizeView.as_view(), name='authorize'),
    path('^yt/oauth2callback/', Oauth2CallbackView.as_view(),
        name='oauth2callback')
]

Metadata

Release files for youtube-django 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for youtube-django 0.2.1
File	Interpreter	ABI	Platform	Actions Reset
youtube_django-0.2.1-py2.py3-none-any.whl 8.7 kB Oct 12, 2018 Without provenance	Python 2, Python 3	none	any	Details for youtube_django-0.2.1-py2.py3-none-any.whl

Release files / youtube_django-0.2.1-py2.py3-none-any.whl

Download URL	youtube_django-0.2.1-py2.py3-none-any.whl
Size	8.7 kB
Tags	Python 2 Python 3
SHA-256 checksum How to use checksums	`df6c2432495f4c3fde6eb6c5caac2b9c06d5b505e347827b3ca50ef917ecabcc`
BLAKE2b-256 checksum How to use checksums	`61581735a25bf433ed1c857f49f096484c8bd4b1a3b24df87e89fea7df87cfa5`
Upload date	Oct 12, 2018
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.0`

Security for youtube-django 0.2.1

Report project as malware

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.