Saravanan666/pypi-org huggingface dataset:
Package: django-data-import-management
django-data-import-managementDjango data import management application.Installpip install django-data-import-managementUsagepro/settings.pyINSTALLED_APPS = [
    ...
    'django_data_import_management',
    'example_app',
    ...
]example_app/import_workflow.pyfrom django_data_import_management.models import DjangoDataImportWorkflow
from django_data_import_management.models import ParsedItem

class ExampleImportWorkflow(DjangoDataImportWorkflow):

    def do_parse(self):
        items = []
        for i in range(10):
            item = ParsedItem()
            info = str(i)
            data = {
                "index": 1,
            }
            item.mark_success(info, data)
            items.append(item)
        return items        # Note: always return the parsed ParsedItems
    
    def do_import(self, import_items):
        for item in import_items:
            item.mark_success()
        return import_items   # Note: always return import_itemsexample_app/apps.pyclass ExampleAppConfig(AppConfig):
    name = 'example_app'

    def ready(self):
        from django_data_import_management.models import register_django_data_import_workflow
        from .import_workflows import ExampleImportWorkflow
        register_django_data_import_workflow("Example Import", ExampleImportWorkflow)example_app/init.pydefault_app_config = "example_app.apps.ExampleAppConfig"Steps:Setup dependencies.Create a new workflow.Register the workflow when project starts.Releasesv0.1.4First release.v0.1.5Pass datafile instance to workflow.v0.1.6Add DjangoSimpleExportedDataImportWorkflow base class.v0.1.8Fix string format problem.Fix fk problem.v0.1.9Fix dependence package version problem.v0.2.0Fix ugettext problem for Django 4.2.x.Add do_parse and do_import object toolbar button.v0.2.1Doc update.
Package: django-datalogger
Datalogger=====[![ENV](https://img.shields.io/badge/python-2.7-green.svg)](https://github.com/pylixm/django-datalogger)[![ENV](https://img.shields.io/badge/django-1.7+-green.svg)](https://github.com/pylixm/django-datalogger)[![LICENSE](https://img.shields.io/badge/license-MIT-green.svg)](https://github.com/pylixm/django-datalogger/master/LICENSE.txt)Datalogger is a simple Django app to record data changes.[中文说明](docs/README_zh.md)Quick start-----------1. Installation.```bashpip install django-datalogger```1. Add `django-datalogger` to your INSTALLED_APPS setting like this::```pythonINSTALLED_APPS = [...'django-datalogger',]```1. Add `datalogger.middleware.common.DataUpadataDeleteMiddleware` to your MIDDLEWARE_CLASSES setting like this::```pythonMIDDLEWARE_CLASSES = (...'datalogger.middleware.common.DataUpadataDeleteMiddleware',)```1. Run `python manage.py makemigrations` and `python manage.py migrate` to create the `django-datalogger` models.1. Start your models inherit `LogOnUpdateDeleteModel` abstract model like this:```pythonclass TestA(LogOnUpdateDeleteModel):name = models.CharField( max_length=128, blank=True)memo = models.TextField()create_at = models.DateTimeField(blank=True, auto_now_add=True)update_at = models.DateTimeField(blank=True, auto_now=True)```1. Change the test model data by the model api.1. You will find the data change log in datalogger models.You can visit http://127.0.0.1:8000/admin/to see these changer.
Package: django-datamaps
django-datamaps provide utility functions to help you utilize datamps.js.Requirements/Installingdjango-datamaps requires Python 2.6-2.7. It also requires Django >= 1.4 and
django-selectable==0.7.0.The easiest way to install django-sticky-uploads is usingpip:pip install django-datamapsRunning the TestsYou can run the tests with via:python setup.py testor:python runtests.pyLicensedjango-sticky-uploads is released under the BSD License. See theLICENSEfile for more details.A bundled version of jQuery 1.10.2 is included the source distribution which is used under
itsMIT license.ContributingIf you think you’ve found a bug or are interested in contributing to this project
check outdjango-datamaps on Github.Development sponsored byRochApps, LLC.
Package: django-data-masker
Data Masker is a simple Django app to do data masking. It masks sensitive data
by name of form fields and is highly configurable. CurrentlyCharFieldandEmailFieldare supported.Quick startAdddata_maskerto your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'data_masker',
]In template, pass the form which contains sensitive data tomask_formtag
before any rendering tags.Example template{# Load the tag library #}{%loaddata_masker%}{# Display a form #}<form action="/url/to/submit/" method="post" class="form">{%csrf_token%}{# Mask the form #}{%mask_formformasmasked_form%}{{masked_form}}{# It also works well with django-bootstrap #}{%comment%}{% bootstrap_form masked_form %}{%endcomment%}<button type="submit">Submit</button>
</form>Settingsdjango-data-masker has some pre-configured settings which can be modified by adding variables withDATA_MASKER_prefix in yoursettings.pyand customizing the values you want.VariableUsageDefaultDATA_MASKER_CLEAR_HEADINGNumber of heading characters to leave untouched2DATA_MASKER_CLEAR_TAILINGNumber of tailing characters to leave untouched2DATA_MASKER_MASK_FULL_EMAILMask full email address including domainname partFalseDATA_MASKER_FIELD_LISTList of field name to mask[‘account_name’, ‘account_number’, ‘email’]
Package: django-data-migration
django-data-migrationis a reusable Django app that migrates your
legacy data into your new django app. The only thing you have to supply
is an appropriate SQL query that transforms your data from the old
schema into your model structure. Dependencies between these migrations
will be resolved automatically. Give it a try!This extension is tested automatically against:Django 1.5Django 1.6Django 1.7on Python 2.7, 3.3 and 3.4.Python 3.2 is not supported, due to aSyntaxError in the future
librarywhich is used to support both Python 2 and 3.InstallationInstall using pip:pip install django-data-migrationAdd toINSTALLED_APPS:'data_migration',Run./manage.py migrateor./manage.py syncdbto create the
included modelsAlternatively, you can adddjango-data-migrationto yourrequirements.txt.DocumentationThe documentation ofdjango-data-migrationis built bysphinxand can be edited in thedocs/directory of this project.Go to the Documentation on Read The
DocsStatus of projectThis app has been extracted out of a production system and some work has
been done, to write tests and refactor code. The project documentation
is a work in progress.Start participatingFork the project on Github and clone it locallyInstall Python 2.7 and 3.3,virtualenvandtoxRun the tests withtoxagainst all supported versions of PythonCreate a Pull Request on Github
Package: django-dataperm-model
django-dataperm-modelA data model containing data permissions.Installpip install django-dataperm-modelsettings.pyINSTALLED_APPS = [
    ......
    'dataperm',
    ......
]Installed UtilsmodelsWithOwnerMixinadminWithOwnerMixinRelease Notesv0.1.0Add models.WithOwnerMixin and admin.WithOwnerMixin.
Package: django-datapurge
Django DatapurgeSimple app to help purging old data like sesions, nonces, logs etc..
It’s likedjango-admin.pyclearsessionscommand but gives you
possibility to purge anything. Simpliest way to usedatapurgeis to
run management command (manually or via cron):python manage.py purgeIt’s easy to integrate datapurge withceleryorkronos. Just
wrapdatapurge.actions.purgefunction with code corresponding to
your task backend and run it the way you want.RequirementsPython (2.6, 2.7, 3.4, 3.5)Django>=1.3.7InstallationInstall from PyPI using pip:pip install django-datapurgeOr clone this repo:git clone git@github.com:swistakm/django-datapurge.gitAdd'datapurge'to yourINSTALLED_APPSsetting.INSTALLED_APPS = (
    ...
    'datapurge',
)ConfigurationAddDATAPURGE_MODELSto your settings file and specify which models
should be purged:DATAPURGE_MODELS = {
    'app_name.ModelName1': {
        # policy settings
        ...
        },
    'app_name.ModelName2': {
        ...
        },
}Available purge policiesThere are a few available policies for your use. Use what you find most
convienient. Policy is guessed from set parameters provided.ExpireFieldPolicyDeletes all objects whichexpire_fielddatetime is older thantimezone.now().Parameters:'expire_field'- name of datetime field holding expiration dateExample:DATAPURGE_MODELS = {
    "sessions.Session": {
        "expire_field": "expire_date",
    }
}LifetimePolicyDeletes all objects which are older than specifiedlifetimeParameters:'lifetime'- timedelta object specifying maximum lifetime of
object'created_field'- name of datetime field holding object creation
timeExample:from timezone import timedelta

DATAPURGE_MODELS = {
    "oauth_provider.Nonce": {
        "lifetime": timedelta(seconds=300),
        "created_field": "timestamp",
    }CallablePolicyDeletes all objects from query returned by provided callableParameters:'callable'- function accepting model class and returning
QuerySetExample:DATAPURGE_MODELS = {
    "some_app.Log": {
        "callable": lambda model: model.objects.all(),
    }
Package: django-data-replication
Django Data ReplicationThis will allow you to replicate data to another place - Like mongo for analytics.Learn morehttps://github.com/icmanage/django-data-replication.Build Process:Update the__version_info__inside of the application. Commit and push.Tag the release with the version.git tag <version> -m "Release"; git push --tagsBuild the releaserm -rf dist build *egg-info; python setup.py sdist bdist_wheelUpload the datatwine upload dist/*
Package: django-data-sdk
settings.INSTALLED_APPSINSTALLED_APPS=[# other apps ..."django_data_sdk",# other apps ...]Install middleware to settings.MIDDLEWAREMIDDLEWARE=["django_data_sdk.middleware.DjangoDataTopMiddleware",# other middlewares"django_data_sdk.middleware.DjangoDataBottomMiddleware",]Configure DJANGO_DATA related settingsDJANGO_DATA_SINK_SETTINGS={"partition_prefix":"default_prefix","partition_by":"request_time",# request_time, response_time in context, and put_time"partition_date_format":"%Y-%m-%d",# default interval day by day"app_secret":None,"backend":"django_data_sdk.sink.backends.DummyBackend",# DummyBackend or KafkaBackend"backend_kwargs":{},"sink_mode":mode.DIRECT,# DIRECT or CELERY}Restart the service and check your data from the sink backend
Package: django-data-seeder
This app provides a simple way of seeding data for your data models into your
development or test database. This can be achieved through the Admin site, via
a management command, or by writing your own scripts that use a seeder object.It is often necessary to be able to seed large datasets, especially in complex
projects, where having pre-loaded data can save time in the development
lifecycle. Additionally, by allowing simple data seeding, you can more
effectively conduct load tests or test complex edge case scnearios.RequirementsDjango 2.2+Python 3.6+InstallationYou can installdata_seederusingpippipinstalldjango-data-seederQuick StartAdddata_seederto yourINSTALLED_APPSinsettings.pyINSTALLED_APPS=[...'data_seeder',]Seed data with the following commandpythonmanage.pyseeddata[options]app.models.Model[app.models.Model2,...]This will generate a single seed for each model provided.Advanced Usage of the Management CommandIn addition to generating single seeds for models, theseeddatacan
also create as many seeds as you wantpythonmanage.pyseeddata--seeds=Napps.model.ModelThis will generateNseeds forapps.model.ModelAnother option that you can use is to generate related models. This is
used for foreign key references where we need to recursively generate
seeds for models. The default behaviour for this is disabled, meaning
that a randomly selected existing model will be used for the related
model field. We override this by doing the followingpythonmanage.pyseeddata--generate-relatedapps.model.ModelOne limitation to this behavior is that the data seeder will not generate
a related model if the relation is the model itself. This would cause an
infinite recursion.For more information about theseeddatacommand, please look at the
help page.pythonmanage.pyhelpseeddataUsing the Django Admin SiteFor convenience, you can also use the out-of-the-box Administrator site
included with Django to generate your seeds.To do this, you must register your models with the admin site using the
customModelAdminclass provided. For example, inadmin.pyfor
your appfromdjango.contribimportadminfrom.modelsimportMyModelfromdata_seeder.adminimportDataGeneratorAdminadmin.site.register(MyModel,DataGeneratorAdmin)This will add a button to the model page in the admin site to generate
data, which will provide you with the same options available in the
management command.You can also register your models using a decorator insteadfromdjango.contribimportadminfrom.modelsimportMyModelfromdata_seeder.adminimportdata_generator_register@admin.register(MyModel)@data_generator_registerclassMyModelAdmin(admin.ModelAdmin):passContributeYou can find the latest development version onGitHub. Feel free to
fork it, file bugs, or contribute.Feel free to send me a message byemailortwitter.
Package: django-data-sniffer
django-data-snifferdjango-data-snifferprovides a set of tools to inspect the data in your
service for misconfigurationsFeaturesConfigurable warning/alert queries on any database table in your django appA view to see all misconfigured objects in your tableAbility to modify your queries via an externally hosted manifest file so
that adding a new health check doesn't require a deploymentComing SoonFilters & groupingSearchPaginationGet manifest file from util method instead of URLJSON API responseNotificationsSetupInstallationpip install django_data_snifferAdd to settings.pyINSTALLED_APPS = (
  ...
  'data_sniffer
  ...
)

DATA_SNIFFER_ENABLED = True
DATA_SNIFFER_MANIFEST_FILE = 'https://path/to/your/manifest/file.json'  # noqaConfiguring the manifest fileHere's an example manifest file{
    "clients": {
        "name": "Active clients healthcheck",
        "model": "yourapp.Client",
        "queryset": {
            "filters": {
                "status": "active"
            },
            "excludes": null,
            "ordering": null,
            "display_field": "name",
            "extra_display_fields": ["id", "membership_type"]
        },
        "alerts": [
            {
                "level": "WARNING",
                "name": "Missing billing",
                "queryset": {
                    "filters": {
                        "billing_configured": false
                    }
                },
                "message": "Client does not have billing set up"
            },
            {
                "level": "ERROR",
                "name": "Missing billing and getting premium features",
                "queryset": {
                    "filters": {
                        "billing_configured": false,
                        "premium_features_enabled": true
                    },
                    "excludes": {
                        "is_demo": true
                    }
                },
                "message": "Client has invalid feature set"
            }
        ]
    }
}
Package: django-data-sources-tracking
Django app for dealing with files/data sources and tracking them. Useful for tracking public annotations or bfx pipeline outputsDocumentationThe full documentation is athttps://django-data-sources-tracking.readthedocs.io.QuickstartInstall Django Data Tracking:pip install django-data-sources-trackingAdd it to yourINSTALLED_APPS(along with DRF and django-filters):INSTALLED_APPS=(...'rest_framework','django_filters',...'data_sources_tracking','user_activities',...)Add Django Data Tracking’s URL patterns:fromdata_sources_trackingimporturlsasdata_sources_tracking_urlsurlpatterns=[...url(r'^',include(data_sources_tracking_urls,namespace='data_sources_tracking')),...]FeaturesTODORunning TestsDoes the code actually work?source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ toxCreditsTools used in rendering this package:Cookiecuttercookiecutter-djangopackageHistory0.1.0 (2017-12-29)First release on PyPI.Initial models and REST API0.2.0 (2018-01-05)0.2.0 ChangelogImproved REST API filters0.2.1 (2018-01-09)0.2.1 ChangelogUpdated packages and fixed issue with migrations0.2.2 (2018-01-12)0.2.2 ChangelogFixed route names for SimpleRouter0.3.0 (2018-02-09)0.3.0 Changelog0.3.1 (2018-03-14)0.3.1 ChangelogUpdated requirementsUpdated choices for file type choices to be more comprehensive0.4.0 (2018-03-23)0.4.0 ChangelogAdded property for File model for easy access to display type0.5.0 (2018-03-30)0.5.0 ChangelogAdded additional file type choices0.6.0 (2018-04-03)0.6.0 ChangelogAdded support for GraphQL0.7.0 (2018-04-07)0.7.0 ChangelogAdded support for GraphQL0.7.1 (2018-04-18)0.7.1 Changelog#27 - Fixed file type issuesUpdated 3rd party libs0.7.2 (2018-05-16)0.7.2 ChangelogUpdated 3rd party libsUpdated setup.py to read from requirements.txt0.8.0 (2018-06-01)0.8.0 ChangelogRemoved support for GraphQL - useless here.  Applications using GraphQL can set up schema with models0.8.1 (2018-08-13)0.8.1 ChangelogUpdated 3rd party requirements. Some requirements had changed so it was causing failures0.8.2 (2018-10-29)0.8.2 ChangelogUpdated 3rd party requirements.0.8.3 (2019-01-08)0.8.3 ChangelogUpdated 3rd party requirements.0.8.4 (2019-02-08)0.8.4 ChangelogUpdated 3rd party requirements.Refactored tests0.8.5 (2019-04-10)0.8.5 ChangelogUpdated 3rd party requirements.Updated travis to use xenial distribution. Django 2.1 dropped support for SQLite < 3.8.30.8.6 (2019-05-31)0.8.6 ChangelogUpdated package to use latest cookiecutter template0.8.7 (2019-07-26)0.8.7 ChangelogUpdated 3rd party requirements.0.8.8 (2019-08-09)0.8.8 ChangelogUpdated 3rd party requirements.Added support for excel file types0.9.0 (2019-09-09)0.9.0 ChangelogUpdated 3rd party requirements.Added FileField and hash (to detect duplicates)0.9.1 (2019-09-09)0.9.1 ChangelogHotfix to fix broken migration.  It could not access create_hash method on File class
Package: django-datastore
Django DatastoreDjango application to either :store unstructured data in JSON format with permission handlingstore files for models through a generic foreign keyAll of that can be handled with a REST API thanks to Django REST Framework.=========
CHANGELOG0.1.3.5           (2020-09-08)Fix: make it possible to read and write with the RelatedDocumentUrlSerializer0.1.3.4         (2020-09-07)Restore deployment with pypi provider0.1.2           (2020-09-03)Create related document url serializerUsing django.db.models.JSONField instead of django.contrib.postgres.fields0.1.1           (2019-12-19)First release
Package: django-datasync
Management command to sync environment data.Syncs database and media, for example when deploying an acceptance environment.Quick Startpip install django-datasyncadd ‘datasync’ to INSTALLED APPSconfigure settingsDATASYNC = {
    'HOST': '{{ remote_host_address }}',
    'PORT': {{ remote_ssh_port }}
    'USER': '{{ remote_username }}',
    'PASSWORD': '{{ remote_user_password }}',
    'MEDIA_REMOTE': '{{ remote_media_directory }}',
    'MEDIA_TARGET': '{{ local_media_directory }}',
    'DATABASE': {
        'HOST': '{{ db_host_address }}',
        'USER': '{{ db_username }}',
        'PASSWORD': '{{ db_password }}',
        'NAME': '{{ db_name }}',
        'PORT': {{ db_port }}
    },
}You will now have access to the management command ‘sync_environment’. Run that command from the target machine, perhaps as a cron job. Or add to ansible-playbooks setup.Supported databases: PostgreSQL.You will also have to edit the following postgres conf files in order to allow access from your target machine(s)/etc/postgresql/[version]/main/pg_hba.conf/etc/postgresql/[version]/main/postgres.confMore information to be found in the PostgreSQL documentation.
Package: django-data-tables
Django Data Tables is a Framework for Django that creates model related Data Tables that fetch
filtered data via AJAX Requests and allow different actions on model instances.This is a reimplementation of a libary that was developed and heavily used in a big inhouse
enterprise software at Studitemps GmbH. This implemetation is still in a very early stage of development.
You can play around but expect a few breaking changes before reaching version 1.0.0.Detailed documentation is still missinig but will be added hopefully soon.Quick start1. Add “django_data_tables” to your INSTALLED_APPS in your settings.py
like this:INSTALLED_APPS = [
    ...
    'django_data_tables',
    ...
]2. Include the autodiscover and  URLconf in your project urls.py
like this:from django_data_tables.utils import autodiscover as ddt_autodiscover
from django_data_tables import views as dt_views

ddt_autodiscover()

...
path('ddt/get_data/<table_name>/', dt_views.get_data, name='ddt-get_data'),
path('ddt/action/<table_name>', dt_views.action, name='ddt-action'),
...3. Create a tables.py in an app where you want
to create a data table with something like this:import django_data_tables as ddt

from .forms import MyEditForm

class EditAction(ddt.FormAction):
     name = 'Edit'
     form_class = MyEditForm

     def success(self, form, obj):
         form.save()


class BaseDataTable(ddt.DataTable):
     columns = [
        ddt.IdColumn('id'),
        ddt.ModelFieldColumn('<some existing field e.g. "name">',
        ddt.ActionColumn('Do')
     ]
     filters = {'id_filter': ddt.IntFilter('id'),}
     actions = [EditAction,]
     model = '<your_app_name>.<YourModel>'4. In your view create a table renderer instance and pass it into the
renderers context. So in your apps views do something like that:from .tables import BaseDataTable

...

def my_fancy_view(request):
    table = BaseDataTable().get_renderer(request)
    return render(request, 'app/my_views_template.html', {'table': table})5. In my_views_template.html render the table (very similar
to django forms:<html>
    <head>
    {{ table.media }}
    </head>
    <body>
        <h1>Example for a Django Data Table Renderer</h1>
        {{ table }}
    </body>
</html>6. Create a route to your view in urls as usual an
test it