Saravanan666/pypi-org huggingface dataset:
Package: django-github-hook
Simple continuous integration for Django developers, taking the form of
a Django app for managing GitHub (or BitBucket) post receive hooks.Tested on Python 2.7, 3.4 and 3.5, with Django 1.8 and 1.9.Usagepip installdjango-github-hookAddgithub_hooktoINSTALLED_APPSin your settings.py./manage.py migrate(or./manage.py syncdb)Add e.g.url(r'^hook/',include('github_hook.urls'))to your
urls.pyurlpatternsLog into the Django admin consoleConfigure your hook with the folowing fields:Name: Hook identifierUser: Repo usernameRepo: Repo namePath: Absolute path to script to executeGo to your repo’s “Service Hooks” settings on GitHub (or BitBucket) and add a
WebHook/POST URL:http[s]://[yourwebsite]/hookThe repo information will be read from the JSON payloadAlternatively, you can specify a specific hook by name:http[s]://[yourwebsite]/hook/nameExamplesThe following snippet show how to connect the webhook to a method using django’s signal mechanism.
Note that path must be set to “send-signal” in the hook object instead of an absolute path to a script.fromgithub_hook.modelsimporthook_signaldefprocessWebhook(sender,**kwargs):forkey,valueinkwargs.iteritems():printkey,valuehook_signal.connect(processWebhook)
Package: django-github-issues
Django App to sync GitHub issuesDocumentationThe full documentation is athttps://django-github-issues.readthedocs.io.QuickstartInstall Django GitHub Issues:pip install django-github-issuesAdd it to yourINSTALLED_APPS:INSTALLED_APPS=('rest_framework','django_filters','user_activities',...'github_issues',...)Add Django GitHub Issues’s URL patterns:fromgithub_issuesimporturlsasgithub_issues_urlsurlpatterns=[...url(r'^',include(github_issues_urls,namespace='github_issues')),...]Add the following tosettings.py:GITHUB_API_URL=GITHUB_ACCESS_TOKEN=FeaturesAllows you to sync and track GitHub issues in your project.Allows users who may not have a GitHub user name to post an issue to your project.Running TestsDoes the code actually work?source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ toxCreditsTools used in rendering this package:Cookiecuttercookiecutter-djangopackageHistory0.1.0 (2018-01-18)First release on PyPI.
Package: django-github-log
Create an issue group by error on github when django raises errorInstallationAdd following settings dictionary in your settings.py (LABELS is
optional)GITHUB_LOG_SETTINGS={'USER':'REPOSITORY-OWNER','REPO':'REPOSITORY-NAME','TOKEN':'GITHUB-API-TOKEN','LABELS':['priority:normal','type:error',...]}Add “github_log” in INSTALLED_APPSAdd logging handler in settings.Logging[‘handlers’]'github':{'level':'ERROR','class':'github_log.log.GitHubIssueHandler'},Finally,python manage.py syncdb
Package: django-github-s3
django-github-s3InstallationInstalling from PyPi:$ pip install django-github-s3Once the installation is done, setup the following in the settings.py file.Include the following package in the INSTALLED_APPSINSTALLED_APPS = [
        ....
        'github_storages',
   ]After including the package setup the following in the settings.pyDEFAULT_FILE_STORAGE = "github_storages.backend.BackendStorages"
   GITHUB_HANDLE = "Your Github Handle"
   ACCESS_TOKEN = "Your Github Access Token"
   GITHUB_REPO_NAME = "Your New Github Public Repository Name"
   MEDIA_BUCKET_NAME = "Your media bucket name"For Example:DEFAULT_FILE_STORAGE = "github_storages.backend.BackendStorages"
   GITHUB_HANDLE = "vivekchandrabs"
   ACCESS_TOKEN = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
   GITHUB_REPO_NAME = "Example-Test-Repo"
   MEDIA_BUCKET_NAME = "media"Here is a video on how to get theGitHub Access TokenIf you are using ImageField or FileField upload_to parameter can be specified for better organization of files.photo = models.ImageField(upload_to="pics/", null=True, blank=True)Aboutdjango-github-s3 is a project to provide beginners a storage backend on github for free.Since other simple-storage-services requires credit-card information to setup an account and get started.
There is a lot of traction in between for the beginners.Therefore django-github-s3 helps beginners to store the media files on github with very less number of steps required in the initial setup.Found a Bug? Something Unsupported?Issues are tracked via GitHub issues at theproject issue page.ContributingCheck for open issuesat the project issues page or open a new issues to start a discussion about a feature or bugFork thedjango-github-s3 repository on GitHubto start making changes in your own branch.Warning !!!The github repository that you have to create should be public. Storing any confidential information is not recommended.Thanks To:Vidyadhar Sharmafor guiding me throughout this project.Speckbit Exploratoriesfor giving me this opportunity.
Package: django-github-sso
Easily integrate GitHub Authentication into your Django projectsWelcome to Django GitHub SSOThis library aims to simplify the process of authenticating users with GitHub in Django Admin pages,
inspired by libraries likedjango-admin-ssoDocumentationDocs:https://megalus.github.io/django-github-sso/Install$pipinstalldjango-github-ssoConfigureAdd the following to yoursettings.pyINSTALLED_APPS:# settings.pyINSTALLED_APPS=[# other django apps"django.contrib.messages",# Need for Auth messages"django_github_sso",# Add django_github_sso]Navigate tohttps://github.com/organizations/<YOUR ORGANIZATION>/settings/applications, then select or create a newOrg OAuth App.  From that, retrieve yourClient IDandClient Secret.On the same page, add the addresshttp://localhost:8000/github_sso/callback/on the "Authorization callback URL" field.Add both credentials in yoursettings.py:# settings.pyGITHUB_SSO_CLIENT_ID="your Client ID here"GITHUB_SSO_CLIENT_SECRET="your Client Secret  here"Let Django GitHub SSO auto create users which have access to your repositories:# settings.pyGITHUB_SSO_NEEDED_REPOS=["example/example-repo"]# user needs to be a member of all repos listedInurls.pyplease add theDjango-Github-SSOviews:# urls.pyfromdjango.urlsimportinclude,pathurlpatterns=[# other urlpatterns...path("github_sso/",include("django_github_sso.urls",namespace="django_github_sso")),]And run migrations:$pythonmanage.pymigrateThat's it. Start django on port 8000 and open your browser inhttp://localhost:8000/admin/loginand you should see the
GitHub SSO button.LicenseThis project is licensed under the terms of the MIT license.
Package: django-github-webhook
A class based view for Django that can act as an receiver for GitHub webhooks. It is designed to validate all requests through theirX-Hub-Signatureheaders.Handling of GitHub events is done by implementing a class method with the same name as the event, e.g.ping,pushorfork. See the documentation for
more in-depth information and examples.Free software: BSD licenseInstallationpip install django-github-webhookDocumentationhttps://django-github-webhook.readthedocs.org/DevelopmentTo run the all tests run:toxNote, to combine the coverage data from all the tox environments run:Windowsset PYTEST_ADDOPTS=--cov-append
toxOtherPYTEST_ADDOPTS=--cov-append toxChangelog0.1.0 (2016-01-29)First release on PyPI.
Package: django-github-webhook27
NOTE: This is a fork modified to work on python 2.7A class based view for Django that can act as an receiver for GitHub webhooks. It is designed to validate all requests through theirX-Hub-Signatureheaders.Handling of GitHub events is done by implementing a class method with the same name as the event, e.g.ping,pushorfork. See the documentation for
more in-depth information and examples.Free software: BSD licenseInstallationpip install django-github-webhookDocumentationhttps://django-github-webhook.readthedocs.org/DevelopmentTo run the all tests run:toxNote, to combine the coverage data from all the tox environments run:Windowsset PYTEST_ADDOPTS=--cov-append
toxOtherPYTEST_ADDOPTS=--cov-append toxChangelog0.1.0 (2016-01-29)First release on PyPI.
Package: django-gitlab-auth
This is a Django login view that authenticates against GitLab.Use it if you own a single GitLab instance that you want to use as
a OAuth Authentication Server between multiple apps.See alsodjango-auth-oidc.RequirementsPython 3.6+.Python 2 is not supported, and won’t ever get supported.Django 1.10+Installationpipinstalldjango-gitlab-authsettings.pyINSTALLED_APPS+=['django_gitlab_auth']urls.pyurlpatterns+=[url(r'^accounts/login/',include('django_gitlab_auth.urls')),]ConfigurationGitLabApp’s redirect URI: http(s)://app-domain/accounts/login/callbackApp’s environment variablesGITLAB_SERVER - Gitlab Server URL - with trailing slash.GITLAB_CLIENT_ID - Client ID received from GitLabGITLAB_CLIENT_SECRET - Client secret received from GitLab
Package: django-gitlab-logging
Django GitLab Logging=====================Django GitLab Logging is a custom log handler that has been written with the purpose of auto-opening (and assigning) issues on GitLab everytime something goes south with backend code.Useful for production deployments, where you want to move the flood of 500 errors you get in your mailbox to your GitLab issue tracker.Django GitLab Logging is smart enough to recognize similar errors, thus not opening blindly a new issue everytime. It is also capable of re-opening closed issues that are encountered again.## Configuration* Add `gitlab_logging` to your INSTALLED_APPS.* Drop **those lines of configuration in your settings.py**, taking care of filling everything:```python# GitLab optionsGITLAB_HOST = 'https://gitlab.server.tld'  # Beware: no trailing slash there!GITLAB_USER = 'gitlab.user'GITLAB_TOKEN = 'USER_GITLAB_TOKEN'         # Get this from GitLab user account informationGITLAB_PROJECT_ID = 114                    # Get the project ID from the DBGITLAB_ASSIGNEE_ID = 2                     # Get the assignee ID from the DB (optional, you can drop this parameter)```* Then, **ensure you have Celery installed with Django**. Django GitLab Logging cannot work without a tasker (here, Celery), since GitLab API calls needs to be done asynchronously to avoid blocking your Web workers in case of network delays or GitLab remote server downtimes.* **Proceed either** a `syncdb` or a `migrate` (depending on if you're using South or not)* **Map the custom GitLab Logging handler**:```python'handlers': {# (....)'gitlab_issues': {'level': 'ERROR','class': 'gitlab_logging.handlers.GitlabIssuesHandler',},},```* **Activate your GitLab logging handler** where you need it:```pythonLOGGING['loggers'] = {'django.request': {'handlers': ['all_console', 'django_file', 'gitlab_issues'],'level': 'DEBUG','propagate': True,},# (....)}```* You're done! :v:## Notes* This module is kept up-to-date with latest GitLab API changes. Thus, ensure you're running the latest GitLab version in time when using Django GitLab Logging!* Django GitLab Logging has been built by the happy folks at [Waaave Network](https://waaave.com/), for their website needs.* You may want to read the following tutorial about Django GitLab Logging: [Automatically open GitLab issues for Django errors](https://waaave.com/tutorial/django/automatically-open-gitlab-issues-for-django-errors/)
Package: django-gitlog
GitLog is a Django app that create reusable commit-log datas for furthur machiningGitLog parse thegit logand save them into the Commit table. Which can let you access it and make it full use of in you website.Detailed documentation is in the “docs” directory.Quick startAdd “gitlog” to your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'gitlog',
]Include the gitlog URLconf in your project urls.py like this:path('gitlog/', include("gitlog.urls", namespace='gitlog')),Runpython manage.py migrateto create the gitlog models.Start the development server and visithttp://127.0.0.1:8000/gitlog/runto run the parse precedure.Visithttp://127.0.0.1:8000/gitlog/to see an example Commit Journal.
Package: django-gitolite
Django GitoliteA basic Django app for using GitoliteConfigurationBy default the Gitolite rc file is~/.gitolite.rc. Follow these steps:AddLOCAL_CODE => "$ENV{HOME}/local",to the rc file.Create~/local/triggers/post-compile/django, it should be executable and
call thegitolitetriggermanagement command.Create~/local/hooks/common/post-receive, it should be executable and call
thegitolitehookmanagement command.AddPOST_COMPILE => ['post-compile/django'],to the rc file.AddPOST_CREATE => ['post-compile/django'],to the rc file.AddSSH_AUTHKEYS => ['post-compile/ssh-authkeys'],to the rc file.This is an examplepost-compile/djangoscript:#!/bin/bash
source ~/virtualenv/bin/activate
export PYTHONPATH=~/site
export DJANGO_SETTINGS_MODULE=settings
python ~/site/manage.py gitolitetrigger $@This is an examplepost-receivescript:#!/bin/bash
source ~/virtualenv/bin/activate
export PYTHONPATH=~/site
export DJANGO_SETTINGS_MODULE=settings
python ~/site/manage.py gitolitehook $@Running as another userThis configuration requiressudoand the current user to be in the same group
as the gitolite user's default group.As the gitolite user, open~/.gitolite.rcand addUMASK =>  0027,. This is
required to be able to readgl-creatorandgl-forked-fromfiles in the
repositories. Next, ensure that the key directory,~/.gitolite/keydirexists
and is writable by the current user. Files in this directory need to be
readable by the gitolite user, to ensure that files are created belong to the
gitolite user's default group usechmod g+rwxs ~/.gitolite/keydir.Next, you need to setupsudoso the gitolite user can use it to run Gitolite
triggers. Insert the following line into/etc/sudoers:%git ALL=(git)NOPASSWD:/usr/bin/gitolite trigger SSH_AUTHKEYSBelow is the following I use on my server:Defaults: site-eyl env_keep += "GL_USER"
%git ALL=(git)NOPASSWD:/usr/bin/gitolite trigger SSH_AUTHKEYS,/usr/bin/gitolite list-phy-repos,/usr/bin/gitolite access *,/usr/bin/gitolite D *

Defaults:git env_keep += "GL_REPO GL_USER GL_BYPASS_ACCESS_CHECKS"
git ALL=(site-eyl) NOPASSWD: /srv/site-eyl/bin/manage gitolitehook,/srv/site-eyl/bin/manage gitolitetrigger *LicenseAll code is licensed under GPL v3.
Package: django-gitrevision
WarningThis module is depricated. Usehttps://github.com/klen/dealerinstead.Django Git Revisionis django application that allows use git last head commit hexstring in views and templates.Описание на русском доступно здесь:http://klen.github.com/git-revision-ru.htmlContentsRequirementsInstallationSetup and useBug trackerContributingContributorsLicenseCopyrightRequirementspython >= 2.5django >= 1.2gitpythonInstallationDjango Git Revisionshould be installed usingpip:pip install django-gitrevisionSetup and useAddgitrevisionto INSTALLED_APPS:INSTALLED_APPS += 'gitrevision',If you want use git revisiononly in templatesadd gitrevision context processor in settings:TEMPLATE_CONTEXT_PROCESSORS += 'gitrevision.context_processors.gitrevision',And useGIT_REVISIONvar in templates:...
<link href="/test.css?{{ GIT_REVISION }}" rel="stylesheet" type="text/css" media="screen" />
<script src="/test.js?{{ GIT_REVISION }}"></script>
...Or if you want use git revision inviews and templates, add gitrevision middleware in settings:MIDDLEWARE_CLASSES += 'gitrevision.middleware.GitRevision',Using in views:def superview( request ):
    git_revision = request.git_revision
    ...Using in templates (with requestcontext):...
<script src="/test.js?{{ request.git_revision }}"></script>
...Maybe you be needed appendGIT_PATHin django settings:GIT_PATH = <path_to_your_git_repository>Bug trackerIf you have any suggestions, bug reports or
annoyances please report them to the issue tracker
athttps://github.com/klen/django-gitrevision/issuesContributingDevelopment of django-gitrevision happens at github:https://github.com/klen/django-gitrevisionContributorsklen(Kirill Klenov)LicenseLicensed under aGNU lesser general public license.CopyrightCopyright (c) 2011 Kirill Klenov (horneds@gmail.com)
Package: django-gitstorage
A Django application to browse a Git repository and build Web applications on top of it.GitStorage is:A Djangostorageto browse the contents of the repository (what you see in your working copy)
from a bare repository (without a working copy);Modelsto enrich Git objects, namely add metadata to blobs and allow access to treesMixinviewsto combine with class-based views to browse the repository and add or remove objects.
on top of the repository;Management commands.GitStorage is built on top ofPyGit2andlibgit2, it does not call Git from the command line.ContentsStorageModelsBlobMetadataTreePermissionViewsRepositoryViewTreeViewMixinBlobViewMixinPreviewViewMixinDownloadViewMixinDeleteViewMixinUploadViewMixinSharesViewMixinShareViewMixinManagement CommandsTestsMigrationsLicenseStorageThe Django storage supports most of the storage API: open, save, exists, listdir… missing features include mtime,
ctime and atime since Git doesn’t directly store those values.The storage is limited just as any Git repository. It is designed for a single writer and many readers. Concurrent
writing is not even tested. No effort was made to optimise read access either. Your mileage may vary.The storage is an interesting proof-of-concept but even the rest of GitStorage loads Git objects directly.ModelsBlobMetadataAdd metadata to the blob, only mimetype for now.TreePermissionOnly admin users are allowed by default. Share access to a tree and its blobs (but not its subtrees) to a regular user.ViewsThese views are designed as the foundation of class-based views like TemplateView and FormView,
and your own business logic.RepositoryViewThe main view that dispatches to a view dedicated to each Git object type (namely blob and tree).Not actually a mixin since it is functional but the dedicated views are mixins (see below).TreeViewMixinDefault view for a tree, lists its contents.BlobViewMixinDefault view for a blob, displays its information.PreviewViewMixinPreview the current blob in the browser if possible, download it otherwise.DownloadViewMixinForce download the current blob.DeleteViewMixinDelete the current blob.UploadViewMixinUpload a new file to the current tree (as a blob).SharesViewMixinList of current tree permissions and removing the selected ones.ShareViewMixinShare access to the current tree to a user by adding a tree permission.Management Commandssync_blobmetadataBrowse the repository to compute metadata for each blob not known yet.To call after pushing new commits to the repository, ideally from a Git hook.Cleaning up of metadata for orphan blobs is not handled.TestsA minimal Django project is shipped to run the test suite. Trymake coverage(100% at the time of this writing).MigrationsGitStorage uses South.LicenseGitStorage is copyright Bors Ltd with ideas from the PyGit2 project.GitStorage is published under the GNU General Public License version 3.
Package: django-git-submodules
=====Django Git Submodules=====Django Submodules is a simple Django app that allows youto manage apps as git submodules instead of pip.This allows you to have a local development version ofthird-party packages and merge changes from upstream.Ideally should only be used in development.These changes should be pushed back to the package repositoryand installed with pip on production.Quick start-----------1. Install django-git-submodules::pip install django-git-submodules2. Clone the the package you want on your project root::git clone https://github.com/tomchristie/django-rest-framework.git3. Import the app in your `settings.py`::from dj_git_submodule import submodulesubmodule.add('django-rest-framework')4. Now you should be able to add the app to `INSTALLED_APPS` and have django find it successfully.5. If you need to import multiple apps, you can use wildcards(through glob)::from dj_git_submodule import submodulesubmodule.add(submodule.locate('custom-apps-*'))
Package: django-git-version
django-git-versionA simple django app that usesgitpythonto provide
templatetag(s) to display git version info from the current repo.InstallationFirst, install this package usingpip$ pip install django-git-versionthen addgit_versiontoINSTALLED_APPSin your Djangosettings.py:INSTALLED_APPS=(...'git_version'...)UsageLoad the templatetag with{%loadgit_tags%}and then use one of{%current_commit_short'.'%}{%current_commit'.'%}Where'.'is the path to the git repo
Package: django-giza
NoteOriginal code is fromhttps://github.com/Aquasys/django-sphinx-autodocThis version has been cleaned up and modified to work as a Django
management command.Django is very nice in that way you can reuse a lot of applications in your
projects. It means for big projects that you’ll get a long list of applications
in your settings.INSTALLED_APP.If you’re using Django with Sphinx and want to autodoc all these apps in a wink
of an eye, then this app is for you.A good combination for documenting your project would be:sphinxcartoucheto avoid polluting your docstrings with rst syntaxdjango-gizato generate the doc from your applicationsdjango-sphinxdocto integrate the sphinx doc in your websiteHow it worksIt will scrape all your .py files in each application listed by INSTALLED_APPS,
then add automodules in your PROJECT/SPHINX_ROOT/auto_modules.rst.You will then see your applications grouped in 2 different categories:Project Appsare applications located in your project directory3rd Party Appsare apps which are somewhere in your pythonpath
(preferably in your virtualenv)Good PracticesAdd a docstring in your application’s__init__.pyfile to describe it.
django-giza will automatically scrape it for you (although__init.__.pyfiles are excluded by default…)Install$ pip installdjango-gizaThen addgizato your INSTALLED_APPS in settings.pyUsage$ ./manage.py gizaYou can also specify the relative path to your docs root:$ ./manage.py giza private/documentationSettingsYou can modify some of the settings used by django-giza:GIZA_DOCS_ROOT:Root path for documentation (absolute path required).defaults to:"PROJECT_ROOT/docs"GIZA_INDEX_DOC:Name of your master document.defaults to:"index.rst"GIZA_FILENAME:Name for the generated modules doc.defaults to:"auto_modules"GIZA_DOC_TITLE:Title for the modules page.defaults to:"Python modules"GIZA_INTERNAL_TITLE:Title for the internal apps section.defaults to:"Project Apps"GIZA_EXTERNAL_TITLE:Title for the external apps section.defaults to:"3rd Party Apps"GIZA_EXCLUDED_APPS:List of applications to exclude. Can use wildcard at the end.defaults to:["django.*","giza"]GIZA_EXCLUDED_MODULES:List of filenames to exclude.defaults to:["__init__.py"]GIZA_AUTOMODULE_OPTIONS:List of options to theautomoduledirective, such as
“private-members” (without colon delimiters)defaults to:["deprecated", "members","private-members","special-members","show-inheritance"]TODOWrite testsimprove the not_relevant stuff to auto exclude a file without class or def
Package: django-gizmo
Django app allowing for configurable targetting of template inclusion tags.InstallationAddgizmoto yourINSTALLED APPSsetting.AddROOT_GIZMOCONFvalue to your projects settings file. This specifies the module in which your configured your gizmos, i.e.:ROOT_GIZMOCONF = 'project.gizmos'In this case we have a module calledprojectcontaining agizmos.pyfile.Create your gizmos config (in this cased namedgizmos.py) file in the form:gizmos = (
    ('<loader name>', '<tag name>', '<slot name>', [['<url_name'>, ]]),
)With:<loader name>being the name you would normally pass to Django’s load tag, i.e.myapp_inclusion_tagsfor{% load myapp_inclusion_tags %}.<tag name>being the name of the tag you want to include, i.e.advertfor{% advert %}.<slot name>being the name of the slot you want the tag to show up in, i.e.home.<url_name>optionalbeing the names of the urls you want the tag to show up in, i.e.home.UsageGizmos are stock standard Django inclusion tags. The only diffirence is that instead of specifying tags within a template you specify tags from a distance by using a gizmo conf file in conjunction with thegizmostag.For example, lets say we have anadverttag specified inmyapp’s inclusion tags which we only want to call in the gizmo slot namedadvertfor the url namedhome:Create your tags as normal.Create your gizmos config file in the form:gizmos = (
    ('myapp_inclusion_tag', 'advert', 'advert', ['home', ]),
)In your template for the home view load the gizmo inclusion tags and include a gizmos tag with a slot name of advert:{% load gizmo_inclusion_tags %}

...some html...

{% gizmos 'home_advert' %}

...some more html...