Saravanan666/pypi-org huggingface dataset:
Package: django-priority-batch
TODO.InstallPrerequisitesMake sure you havePython3.6+ installed on your system. If you don’t have it
yet, followthese instructions.UsingPyPIpip install django-priority-batchUsing source onGitHubpip install https://github.com/genialis/django-priority-batch/archive/<git-tree-ish>.tar.gzwhere<git-tree-ish>can represent any commit SHA, branch name, tag name,
etc. inDjango Priority Batch’s GitHub repository. For example, to install
the latest Django Priority Batch from themasterbranch, use:pip install https://github.com/genialis/django-priority-batch/archive/master.tar.gzContributeWe welcome new contributors. Please, open a GitHub issue or contribute a pull
request.
Package: django-prismriver
Django Prismriver: A light but cool Django admin Theme=======================================================Prismriver is another django-admin theme aiming to be good looking while maintaining maximum compatibility with as many django packages as possible, with zero/minimal dependencies.Aside from that it/will try to be modular with dashboard plugins (not yet implemented) so you can configure it easily the way you prefer.How it looks------------![DjangoCms on Prismriver](https://dl.dropbox.com/u/69084784/prismriver.png)Requirements------------- Django 1.4- 5 mins to configure it.Installation------------- Put the prismriver directory into your Pythonpath/project folder or install it using pip using:- pip install django-prismriver- In settings.py make sure that:- You have staticfiles configured correctly.- You look for templates on a '/templates/'  directory.- You have the following template context processors.TEMPLATE_CONTEXT_PROCESSORS = ('django.core.context_processors.request','django.contrib.auth.context_processors.auth',)- On INSTALLED_APPS make sure you add the 'prismriver' app before django.contrib.admin. For example like this:INSTALLED_APPS = ('prismriver','django.contrib.auth','django.contrib.contenttypes','django.contrib.sessions','django.contrib.sites','django.contrib.messages','django.contrib.staticfiles','django.contrib.admin',)- Run your server and it works!- Now there are some extended settings if you want to customize the sidebar.- **CUSTOM_MENU**: Allows you to enable the custom menu. By default this is false.- **SIDEBAR_APP_MENU**: When the previous option is true, it allows you to create "Folders/Menus" contontaining various models. For example imagine you want to unify the auth and sites apps in one menu with all it's options inside. Well, we do the following:SIDEBAR_APP_MENU = [{"name": "Users and Settings","items": ["auth", "prismriver", "sites"],"icon": "users.png","big_icon": "users_big.png","description": "Manage everything about the users here",},]- **SIDEBAR_LAST_ACTIONS**: Shows the last actions widget thing. By default this is true- **DEFAULT_LABELS** If don't want custom menu but you want to use different labels/icons for your applications you can configure them as following:DEFAULT_LABELS = {"auth/": ["Users and Groups", "users.png", "users_big.png","Manage the application users or groups permissions"],"sites/": ["Site management", "web.png", "web_big.png", "Manages the sites application"]}*The "web_big.png" field is not used, it will be removed on the next updates (old version stuff)*- *For more details you can see prismriver/settings.py*
Package: django-privacy-analytics
Django Privacy AnalyticsDjango Privacy Analytics is a minimalist, performant, and privacy-focused analytics system that runs in your Django app.Do Not TrackDjango Privacy Analytics fully respects the 'Do Not Track' (DNT) header; if a request has DNT enabled, Django Privacy Analyticswill notstore a page view.InstallationInstall Django Privacy Analytics by runningpip install django-privacy-analyticsor addingdjango-privacy-analyticsto yourrequirements.txtAddprivacy_analyticsto yourINSTALLED_APPSsetting.Addprivacy_analytics.middleware.AnalyticsMiddlewareto yourMIDDLEWAREsetting, ideally somewhere towards the end (and afterAuthenticationMiddleware).Create the new necessary models by runningpython3 manage.py migrate.Optionallyadd a place to view the analytics by addingpath('analytics/', include('privacy_analytics.urls'))to your URL routing configuration.AccessCurrently, the dashboard is only visible to superusers. This will be configurable in a future version.SettingsInsettings.py, you can set the following:ANALYTICS_IGNORE_PATHS: ignore requests whose paths start with members of thislist
Package: django-privacyidea-auth
Authenticate against a privacyIDEA server.
(https://www.privacyidea.org/)Installvirtualenv --python=python3.5 Django_python3.5
source Django_python3.5/bin/activate
pip install django-privacyidea-authOr from githubvirtualenv --python=python3.5 Django_python3.5
source Django_python3.5/bin/activate
git clone https://github.com/jeweber/django-privacyidea-auth.git
pip install django-privacyidea-auth/Quick startAdd the following to your project/settings.py:AUTHENTICATION_BACKENDS =  ('django.contrib.auth.backends.ModelBackend',
                            'django_privacyidea_auth.privacyidea_auth.PrivacyIDEA', )
PRIVACYIDEA = {
    'url' : 'https://privacyidea/validate/samlcheck',
    'timeout' : 5,
    'ssl_verify' : False,
    'create_user' : False,
    'update_attributes': True,
    'realm': None,
    'enforce_realm': False,
    }‘url’: url of privacyIDEA server to validate the user‘timeout’: validation timeout in seconds‘ssl_verify’: certificate verification, set to True is strongly advised‘create_user’: if set to True, the user in the django DB will be
created, if PrivacyIDEA returns a successful authentication‘update_attributes’: if set to True, the user attributes in the django
DB will be updated, if privacyidea samlcheck returns user attributes‘realm’: if set, the realm of the user, who tries to authenticate. If
the realm is None, the user is looked up in the default realm‘enforce_realm’: if set, login name must contains ‘@’ too separates realm
from the username
Package: django-privacy-killer
This module allows specifying tracking codes through settings (and therefore
through the environment). It currently supports Google Tag Manager and
Google Analytics tracking codes, but pull requests for adding support for
additional trackers is very welcome!Usage variant 1Install the module usingpip installdjango-privacy-killerAddprivacy_killertoINSTALLED_APPSand add the list of tracking
IDS to your settings asPRIVACY_KILLER_IDS =['GTM-****','UA-****',...](Note! This is a stupid example – specifying both GTM and UA codes is
probably not what you wantLoad the template tag library ({% load privacy_killer %}) and add the
two tags,{% privacy_killer_head %}near the<head>of your site,
and{% privacy_killer_body %}near the<body>element.Usage variant 2Do not use this module, and also do not use any trackers at all.Supported trackersGoogle Tag Manager (GTM-****)Google Universal Analytics (UA-****)Facebook Pixel (Prefix the****code withFBQ-when specifyingPRIVACY_KILLER_IDS)DocumentationGithub
Package: django-private-chat2
1.0.2 (2022-01-07)Improve performance for file selection in MessageModelList via ‘prefetch_related’Split consumers.py into separate files for better readability & add strong typingFix typo for ErrorOccuredFix readme1.0.1 (2021-12-23)Remove unneeded files from release1.0.0 (2021-12-23)Support django 4.0Switch to GithubCI instead of travisSeems good enough to make it 1.0.00.1.4 (2021-04-01)File upload functionality0.1.3 (2021-03-29)Fix migrations0.1.2 (2021-03-23)Fix errors found with tests №20.1.1 (2021-03-23)Fix errors found with tests0.1.0 (2021-03-21)First release on PyPI.
Package: django-private-files
=====================django-private-files=====================This application provides utilities for controlling access to static files based onconditions you can specify within your Django application.It provides a ``PrivatedFileField`` model field and appropriate signals for monitoring access to static content.The basic goal is that you should be able to specify permissions for each ``PrivateFileField`` instance inone method (or callable) and leave the rest to django-private-files.Additionally you should be able to switch server (eg. from nginx to lighttpd) without hassle and removethis application from your project without changes to your database.It supports the following methods for limiting access to files:* Basic - files are served with Python (not recommended for production if you have another choice)* Nginx (X-Accel-Redirect) - you can specify protected locations within your nginx configuration file* xsendfile - Apache (with mod_xsendfile), lighttpd and cherokee (not tested yet)It's currently been tested with Django (1.9, 1.10, 1.11 and 2.0), Apache and Nginx. It should work with olderversions of django. Cherokee and lighttpd use the same mechanism as Apache mod_xsendfile, soit should work, but it's not been tested or documented.The full documentation for the project can be found on `Read the Docs <http://django-private-files.rtfd.org/>`_ .
Package: django-private-files-0.1.2
** Just re-uploaded package because it wasn't available as "django-private-files" **=====================django-private-files=====================This application provides utilities for controlling access to static files based onconditions you can specify within your Django application.It provides a PrivatedFileField model field and appropriate signals for monitoring access to static content.The basic goal is that you should be able to specify permissions for each PrivateFileField instance inone method (or callable) and leave the rest to django-private-files.Additionally you should be able to switch server (eg. from nginx to lighttpd) without hassle and removethis application from your project without changes to your database.It supports the following methods for limiting access to files:* Basic - files are served with Python (not recommended for production if you have another choice)* Nginx - you can specify protected locations within your nginx configuration file* xsendfile - Apache (with mod_xsendfile), lighttpd and cherokee (not tested yet)It's currently been tested with Django 1.3, Apache, Nginx and Lighttpd. It should work with older versions ofdjango except for the example project. Cherokee uses the same mechanism as Apache mod_xsendfile and lighttpd, soit should work, but it's not been tested or documented.The full documentation for the project can be found on `Read the Docs <http://django-private-files.rtfd.org/>`_ .
Package: django-privates
Simple private media integration for Django.What does it do?Django supports file uploads for user-generated content out of the box, which is
typicallypublic- think of images, videos…However, often you want to expose files only to correctly authenticated users because
they have a sensitive nature, for example invoice PDFs or tenant-specific documents.django-privates achieves the latter while being as convenient as Django’s coreFileFieldand derivatives.UsageThe installation and usagedocumentationis hosted on ReadTheDocs.
Package: django-privatesite
django-privatesite==================Django custom admins.Don`t reinvent the bicycle and use django.contrib.admin everywhere.[![Downloads](https://pypip.in/d/django-privatesite/badge.png)](https://crate.io/packages/django-privatesite)BENEFITS of django.contrib.admin--------------------------------* Used access control from django.contrib.admin* Used inlines (generic inlines)* Used fieldsets* Used filters* Used Actions* Delete Confirmation* Object history* Pagination* Widgets for dates, raw id fieldINSTALLATION------------Install from pypi, with pip::pip install django-privatesiteAdd ``privatesite`` to ``INSTALLED_APPS``::INSTALLED_APPS = ("privatesite", ) + ('django.contrib.admin', ...)Please note, that ``privatesite`` app must be upperthen ``django.contrib.admin app`` in ``INSTALLED_APPS`` listto overload ``admin/base_site.html`` templateUSAGE------------from privatesite.admin import CustomAdminSitesite1 = CustomAdminSite(name="site1", app_name="admin")class MyPrivateZone(CustomAdminSite):admin_base_template = 'my_zone/base.html'site2 = MyPrivateZone(name="zone", app_name="admin")personal = CustomAdminSite(name="personal", app_name="admin")register models nowfrom myapp.models import Car, Animal, Humansite1.register(Car)site2.register(Car)site2.register(Animal)site2.register(Human)personal.register(Human)in urls.pyurlpatterns += patterns("",(r'^manage/admin/', include(site1.urls)),(r'^private/admin/', include(site2.urls)),(r'^personal/', include(personal.urls)),)And go to see, whats happen.In template you may use{% url 'site1:myapp_car_changeview' %}{% url 'site2:myapp_car_change' car_id %}{% url 'personal:myapp_human_history' human_id %}If you want to add custom views, use this helperhttps://github.com/ionelmc/django-admin-utilsTODO------* don`t work with django-admin-tools now (fix in near future)* write tests
Package: django-probes
Django-probesProvides a Django management command to check whether the primary database
is ready to accept connections.Run this command in a Kubernetes or OpenShiftInit Containerto make
your Django application wait until the database is available (e.g. to run
database migrations).Why Should I Use This App?wait_for_databaseis asinglecommand foralldatabase engines
Django supports. It automatically checks the database you have configured
in your Django project settings. No need to code a specific wait command
for Postgres, MariaDB, Oracle, etc., no need to pull a database engine
specific container just for running the database readiness check.InstallationThe easiest way to install django-probes is with pip$pipinstalldjango-probesBasic UsageAdd django-probes to your Django application:INSTALLED_APPS=[...'django_probes',]2. Add anInit Containerto your Kubernetes/OpenShift deployment
configuration, which calls thewait_for_databasemanagement command:-kind:DeploymentapiVersion:apps/v1spec:template:spec:initContainers:-name:wait-for-databaseimage:my-django-app:latestenvFrom:-secretRef:name:djangocommand:['python','manage.py','wait_for_database']Use with Your Own CommandAlternatively, you can integrate thewait_for_databasecommand in your
own management command, and do things like database migration, load initial
data, etc. with roughly the same Kubernetes setup as above.fromdjango.core.managementimportcall_command# ...call_command('wait_for_database')Command Line OptionsThe management command comes with sane defaults, which you can override
if needed:–timeout, -t:how long to wait for the database before timing out (seconds), default:180–stable, -s:how long to observe whether connection is stable (seconds), default:5–wait-when-down, -d:delay between checks when database is down (seconds), default:2–wait-when-alive, -a:delay between checks when database is up (seconds), default:1–database:which database ofsettings.DATABASESto wait for, default:default
Package: django-processedfilefield
django-processedfilefield: Post-processing for Django FileFields. Takes a dict
of field names on the model, mapped to post-processing functions. These
functions could convert a PDF to text, thumbnail an image, etc.Example:>>> class TestModel(models.Model):
...     content = ProcessedFileField(upload_to='content', variations=dict(
...         content_first_10_bytes=lambda file: file.read()[:10]
...     ))
...     content_first_10_bytes = models.FileField(upload_to='content_first_10_bytes')
...
>>> obj = TestModel.objects.create()
>>> obj.content = ContentFile('abcdefghijklmnopqrstuvwxyz')
>>> obj.content.name = 'alphabet'
>>> obj.save()
>>>
>>> assert obj.content_first_10_bytes.read() == 'abcdefghij'
Package: django-processengine
=====Process Engine=====Process Engine is used in conjunction with celery to create async process fromcelery tasks via an APIQuick start-----------1. Add "processengine" to your INSTALLED_APPS setting like this::INSTALLED_APPS = [...'processengine',]2. Include the router URLconf in your project urls.py like this::from processengine.api import router as process_router...urlpatterns = [url(r'^processengine/', include(process_router.urls)),...]3. Add the PROCESS_MAP settings with your processes and the tasks to run likeso::PROCESS_MAP = {'my.process': ['path.to.taskfile.task',],...}3. (Optional) Add settings for Slack Notifications. Note that it is an error to add a SLACK_WEBHOOK setting without also having the other settings below present.::SLACK_WEBHOOK = "https://hooks.slack.com/services/T051CQH14/VWVRAAFA5/lPz2y84gM0JUoVllBow0Glcx"SLACK_PROCESS_CHANNEL = "#Processes"SLACK_PROCESS_USERNAME = "Someuser"SLACK_PROCESS_EMOJI = ":ghost:"SERVICE_NAME = "Someservice"4. Run `python manage.py migrate` to create the processengine models.5. to create a process run a POST to http://127.0.0.1:8000/processengine/process/with the following data::data = {name: "my.process", # This is the name of your process set in PROCESS_MAP variablecontext: {"name": "value" # This is the data that you pass through to your task}}Note: Your tasks need to conform to the pattern of json in and json out
Package: django-procmail
Django procmail is a Django application allowing to edit procmail’s procmailrc files.A demo is avaible athttp://procmail-demo.genua.fr/with username/password demo/demo.RequirementsDjango>= 1.7 < 1.10pyprocmaildjango-formtoolsif Django version >= 1.8InstallationInstall with pip:sudo pip install pyprocmailor from source code:sudo make installQuick startAddprocmailto your INSTALLED_APPS setting like this:INSTALLED_APPS = (
    'django.contrib.admin',
    ...,
    'procmail',
)For internatinalization support, adddjango.middleware.locale.LocaleMiddlewareto your MIDDLEWARE_CLASSES setting like this:MIDDLEWARE_CLASSES = (
    ...
    'django.middleware.locale.LocaleMiddleware',
    ...
)Include theprocmailURLconf in your project urls.py like this:urlpatterns = [
    url(r'^admin/', admin.site.urls),
    ...
    url(r'^procmail/', include('procmail.urls', namespace="procmail")),
]Start the development server and visithttp://127.0.0.1:8000/procmail/to edit your procmailrc.SettingsAll settings are optional. Add them tosettings.pyto customizedjango-procmail:PROCMAIL_INPLACE: Shoulddjango-procmailtry to edit procmailrc inplace ?
The default isTruePROCMAIL_DEBUG_DIR: WhenPROCMAIL_INPLACEis False, where do we copy procmailrc files for
edition. The default isNone, no dir defined. The default will crash ifPROCMAIL_INPLACEis False.PROCMAIL_TEST_PROCMAILRC: Path to a procmailrc file, used for every user when defined.
It is here for testing purpose. The defaut isNone.PROCMAIL_FALLBACK_ENCODING: Which encoding to use for reading procmailrc files when
charset autodetection failed. The default is'ISO-8859-15'. You should always use
single-byte encodings of this parameter.PROCMAIL_DEFAULT_ENCODING: Chich encoding to use for reading and writing procmailrc files.
If read failed (bad charset), we try to autodetect the charset, is the autodetection failed, we
fallback toPROCMAIL_FALLBACK_ENCODING. The default is'utf-8'.PROCMAIL_DEFAULT_PROCMAILRC: The content of the created procmailrc file when the user do not
already have a procmailrc file.PROCMAIL_VENDOR_CSS: A dictionnary with two keys'bootstrap'and'font-awesome'.
The url to bootstrap3 and fontawesome CSS. The default are"//maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css"and"//maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css".PRCOMAIL_VENDOR_JAVASCRIPT: A ordered dictionnary with four keys'jquery','jquery-ui','sortable','bootstrap'. The default are respectively"//code.jquery.com/jquery-1.11.3.min.js","//code.jquery.com/ui/1.11.4/jquery-ui.js",//cdn.jsdelivr.net/sortable/latest/Sortable.min.js"and"//maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js".
Package: django-prodperfect
django-prodperfectDjango template tags for the ProdPerfect tracking snippet.Installationpip install django-prodperfectAdd toINSTALLED_APPSin yoursettings.pyprodperfect,In your templates, loadprodperfectExample template{% load prodperfect %}


<body>
    ...
    {% tracking_snippet %}
</body>Example settings.pyYou can copy these values from the ProdPerfect provided tracking snippet.PRODPERFECT={'HOST':'prodperfect.datapipe.prodperfect.com/v1','WRITE_KEY':'12345','PROJECT_ID':'12345','TRACKING_LIBRARY_URL':'https://prodperfect.trackinglibrary.prodperfect.com/keen-tracking.min.js'}To override the default tracking behavior, you can change the value of the following properties.PRODPERFECT={# ...'OPTIONS':{'ignoreDisabledFormFields':False,'recordClicks':True,'recordFormSubmits':True,'recordInputChanges':True,'recordPageViews':True,'recordPageUnloads':True,'recordScrollState':True}}Bugs and suggestionsIf you have found a bug or if you have a request for additional functionality, please use the issue tracker on GitHub.https://github.com/prodperfect/django-prodperfect/issuesAuthorDeveloped and maintained byprodperfect.
Package: django-product-catalog
An simple app to manage the products in a catalog (portfolio for example)[under development …]RequirementsDjango 1.11django-mptt 0.8.7Pillow 4.2.1django-extensions 1.9.1Quick startAdd “product_catalog” to your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'product_catalog',
    'mptt',
    'django_extensions',
]Include the product_catalog URLconf in your project urls.py like this:url(r'^catalog/', include('product_catalog.urls'))Runpython manage.py migrateto create the product_catalog models.Start the development server and visithttp://127.0.0.1:8000/admin/to create a product / categories (you’ll need the Admin app enabled).Visithttp://127.0.0.1:8000/catalog/.Optionalif you want to use front-end product management, you must addproduct_catalog.context_processors.product_front_managementto thecontext_processors:TEMPLATES = [
    {
        [...]
        'OPTIONS': {
            'context_processors': [
                [...]
                'product_catalog.context_processors.product_front_management'
            ],
        },
    },
]Settings parametersPRODUCT_CATALOG_PAGINATIONDefault value:10
Integer used to paginate the products.PRODUCT_CATALOG_PRODUCT_BASE_MODELDefault value:‘product_catalog.models.product_abstract.AbstractProduct’
String defining the base model path for the Entry model.PRODUCT_CATALOG_UPLOAD_TODefault value:‘uploads/product_catalog/%Y/%m/%d/’
Path to upload image# Add / Update / Delete on front settingsPRODUCT_CATALOG_FRONT_MANAGEMENTDefault value:True
If ‘True’ allow to manage (create/update/delete) products in front.
False to deactivatePRODUCT_CATALOG_PERMISSION_OPTIONS_SUPERUSER = 0PRODUCT_CATALOG_PERMISSION_OPTIONS_STAFF = 1PRODUCT_CATALOG_PERMISSION_OPTIONS_OWNER = 2PRODUCT_CATALOG_ACCESS_PERMISSIONDefault value:PRODUCT_CATALOG_PERMISSION_OPTIONS_OWNERPRODUCT_CATALOG_FORM_FIELDSDefault value:[‘title’, ‘status’, ‘excerpt’, ‘content’, ‘categories’, ‘image’]
list of available fields in update and create product formPRODUCT_CATALOG_FORM_UPDATE_FIELDSDefault value:FORM_FIELDS
list of available fields in update product formPRODUCT_CATALOG_FORM_CREATE_FIELDSDefault value:FORM_FIELDS
list of available fields in create product form
Package: django-production-ready
A simple app with a single management command that checks if your project is
production ready.InstallIf you usepip:$ pip install django-production-readyorCheckout the source code fromgithuband:$ python setup.py installAdd the app to yourINSTALLED_APPSin thesettings.py.INSTALLED_APPS = (
…
prodready,
…
)UsageRun the management command to run the tests:$ python manage.py is_it_ready