Saravanan666/pypi-org huggingface dataset:
Package: django-tasker
Dead simple async task queue. Stores tasks in database.
No overhead infrastructure required just for throwing something off process.https://github.com/wooyek/django-taskerUsageYou are free to make task from function or class and instance methods. No boilerplate functions are required to wrap task logic.With django models instances tasks will remember an instance primary key, load an instance and call a method.classSomeModel(models.Model):...@queueabledefupdate_this_instance(self,*args,**kwargs):...defmust_do_something(self):...self.update_this_instance.queue()...With plain old class object tasks will call it’s classmethod. Normal functions are also supported.classPocoClass(Object):@queueabledefdo_stuff_with_models(cls,limit):...@queueabledefbackground_job(cls,with_this,and_that):...PocoClass.do_stuff_with_models.queue(10)background_job.queue(foo,bar)Limited support for arguments serializationCall arguments are supported as long as they are json serializable and they’re serialized up to aTaskInfo.payloadfieldsmax_length.
We don’t wan;t to be holding too much information, preferably models instances are holding just enough information for parametrize task execution.Why not Celery?Celeryis great! But it’s sometimes an overkill. It’s a full-on messaging implementation with all the bells and whistles
you need for sending tasks to some worker andgetting a result back.Maintaining all that infrastructure just to send an email every couple of request seems a bit too much.Why not RQ?Python-RQis super. But it need’s Redis. It’s fine when your background work does not pile up.
Using Redis to hold gigabytes of task data is like burning money.Why DB as storage?Because you already have it, it’s the simplest storage to use. And with fanout resulting in millions
of tasks the only cheaper storage is disk.Why not fire up more workers?Sometimes you just can’t crunch task quick enough, for eg. because of the API throttling limits. It’s more sensible
to store them and spread execution in time.
Package: django-tasker-account
FeaturesGeocoding user (Automatic determination of the user’s location during registration)Automatic time zone change depending on user settingsAutomatic language change depending on user settingsUser ProfileTimezoneLanguageGenderBirth dateMobile phoneAvatarOAuthProviderGoogleFacebookVK.comYandexFilling user profile from provider OAuthAutomatic download avatarPagesLogin pageSign up page (sending a confirmation email)Page forgot passwordUser profile pagePage change passwordPage change firstname, lastname, gender, birth datePage change country and citySet 2FAUpload avatarRequirementsPython 3.6+A supported version of Django (currently 2.2)Getting ItYou can get Django Tasker Account by using pip:$ pip install django-tasker-accountIf you want to install it from source, grab the git repository from GitHub and run setup.py:$ git clone git://github.com/kostya-ten/django_tasker_account.git
$ cd django_tasker_account
$ python setup.py installInstallationTo enabledjango_tasker_accountin your project you need to add it toINSTALLED_APPSin your projectssettings.pyINSTALLED_APPS=(# ...'django_tasker_account','django_tasker_geobase','mptt',# ...)Full documentation
Package: django-tasker-unisender
RequirementsPython 3.6+A supported version of Django >= 2.0InstallationYou can get Django Tasker Unisender by using pip:$ pip install django-tasker-unisenderTo enabledjango_tasker_unisenderin your project you need to add it toINSTALLED_APPSin your projectssettings.pyINSTALLED_APPS=(# ...'django_tasker_unisender',# ...)Add to yoursettings.pyUNISENDER_API_KEY="<< YOU API KEY>>"You can get the api key at thislinkAdd to yourmodels.pyfromdjango_tasker_unisender.modelsimportEmailModelclassSubscribe(EmailModel):classUnisenderMeta:list_id=123456789# Your list id contact on UnisenderMigrate your projectpythonmanage.pymakemigrationspythonmanage.pymigrateAdd to youradmin.pyfromdjango.contribimportadminfrom.importmodelsclassSubscribeAdmin(admin.ModelAdmin):list_display=('email',)admin.site.register(models.Subscribe,SubscribeAdmin)Full documentation
Package: django-task-manager
fsf_2019_screening_task1django-task-manager is pluggable, multi-user, mulyi-team task management
and assignment application for Django, designed to be used into an existing site as a reusable app.
django-task-manager can be user as personal to-do tracker or team task managment system.
django-task-manager is developed as screening task for felloship from fossee for year 2019.FeaturesSearchComments on tasksMobile-friendlySeparate view for My Tasks and completed tasksRequirementsDjango 2.0+Python 3.6+Installationdjango-task-manager is a Django app, not a project site. It needs a site to live in.Put fsf_2019_screening_task1/task_manager somewhere on your Python path, or install via pip:pip install django-task-managerAdd to your settings:INSTALLED_APPS = (
    ...
    'task-manager',
)Create database tables:python manage.py migrate task_managerAdd to your URL conf:path('task-manger/', include('task_manager.urls')),django-task-manager makes use of the Djangomessagessystem. Make sure you have installedmessages.Running Testspython manage.py test task_managerOverviewTeam can be created by any authenticated user. User that creates team is the leader of team.
Leader has permissions to add members to team using their username.
Lerder can revove team members using the remove button.
Leader can delete team only if team has no members except leader.
Only leader is allowed to assign tasks to his team.Any authenticated user can create tasks. Task can be assigned to team he is leading.
After assigning task to a team, creator can edit the task to assign task to members of team.
Newly created task is marked as Planned. After a assigned user accepts the task, it is marked as In-Progress.
Task can be marked as Completed by any assigned user or creator.
Task can only be edited by creator if task is Planned(if task is In-Progress, assigned users has alreary started working on it, if there are any update comments can be used).Assigned users and team members can comment on task.Task assigned to team wich are not completed are shown on task detail page.
Tasks whose due date is passed are shown with red background.Tasks assigned to user wich are not completed are shown on my-tasks page.
Tasks whose due date is passed are shown with red background.Completed tasks can be seen on completed-tasks page.User can search tasks by keyword.
Tasks wich contain that keyword in title or description are shown to user(Only tasks user is allowed to see are shown)User from another team is not allowed to see or comment on task
Package: django-tasksoftheday
=====Tasks of the Day=====Polls is a simple Django app to conduct Web-based polls. For eachQuick start-----------1. Add "polls" to your INSTALLED_APPS setting like this::INSTALLED_APPS = (...'tasksoftheday',)2. Include the polls URLconf in your project urls.py like this::url(r'^tasksoftheday/', include('tasksoftheday.urls')),3. Run `python manage.py migrate` to create the tasksoftheday models.4. Start the development server and visit http://127.0.0.1:8000/admin/to create a poll (you'll need the Admin app enabled).5. Visit http://127.0.0.1:8000/tasksoftheday/TODO----- add multiple tasks at once screen (faster input)- add tomorrow button on datepicker field
Package: django-tasktracker
Task Tracker is a basic Django app to record and track stories, tasks
and invested time. Loosely based on Extreme Programming methodology.Quick startUse an old Django project or start a new project in desired location:$ django-admin startproject mysiteIn your project settings.py add “tracker” to INSTALLED_APPS like this:INSTALLED_APPS = [
    ...
    'tracker',
]Include the tracker URLconf in your project urls.py like this:path('tracker/', include('tracker.urls')),Create Task Tracker models by runing:$ python manage.py migrateStart the development server:$ python manage.py runserverVisithttp://127.0.0.1:8000/tracker/.TestsApp has inbuilt tests that require Selenium set up. Seehttp://www.seleniumhq.orgfor more details.
Package: django-tastypie
Creating delicious APIs for Django apps since 2010.Currently in beta but being used actively in production on several
sites.RequirementsCorePython 3.6+, preferably 3.8+ (Whatever is supported by your version of Django)Django 4.2, 3.2 (LTS releases), or Django 4.0 / 4.1 (intermediate releases)dateutil (http://labix.org/python-dateutil) >= 2.1Format SupportXML: lxml 3 (http://lxml.de/) and defusedxml (https://pypi.python.org/pypi/defusedxml)YAML: pyyaml (http://pyyaml.org/)binary plist: biplist (https://bitbucket.org/wooster/biplist)OptionalHTTP Digest authentication: python3-digest (https://bitbucket.org/akoha/python-digest/)What’s It Look Like?A basic example looks like:# myapp/api.py# ============fromtastypie.resourcesimportModelResourcefrommyapp.modelsimportEntryclassEntryResource(ModelResource):classMeta:queryset=Entry.objects.all()# urls.py# =======fromdjango.urls.confimportre_path,includefromtastypie.apiimportApifrommyapp.apiimportEntryResourcev1_api=Api(api_name='v1')v1_api.register(EntryResource())urlpatterns=[# The normal jazz here then...re_path(r'^api/',include(v1_api.urls)),]That gets you a fully working, read-write API for theEntrymodel that
supports all CRUD operations in a RESTful way. JSON/XML/YAML support is already
there, and it’s easy to add related data/authentication/caching.You can find more in the documentation athttps://django-tastypie.readthedocs.io/.Why Tastypie?There are other API frameworks out there for Django. You need to
assess the options available and decide for yourself. That said, here are some
common reasons for tastypie.You need an API that is RESTful and uses HTTP well.You want to support deep relations.You DON’T want to have to write your own serializer to make the output right.You want an API framework that has little magic, very flexible and maps well to
the problem domain.You want/need XML serialization that is treated equally to JSON (and YAML is
there too).Reference Materialhttps://django-tastypie.readthedocs.io/en/latest/https://github.com/django-tastypie/django-tastypie/tree/master/tests/basicshows
basic usage of tastypiehttp://en.wikipedia.org/wiki/RESThttp://en.wikipedia.org/wiki/List_of_HTTP_status_codeshttp://www.ietf.org/rfc/rfc2616.txthttp://jacobian.org/writing/rest-worst-practices/Getting HelpThere are two primary ways of getting help.Go toStackOverflowand post a question with thetastypietag.We have an IRC channel (#tastypie on irc.freenode.net) to get help,
bounce an idea by us, or generally shoot the breeze.SecurityTastypie is committed to providing a flexible and secure API, and was designed
with many security features and options in mind. Due to the complex nature of
APIs and the constant discovery of new attack vectors and vulnerabilities,
no software is immune to security holes. We rely on our community to report
and help us investigate security issues.If you come across a security holeplease do not open a Github issue.
Instead,drop us an emailattastypie-security@googlegroups.comWe’ll then work together to investigate and resolve the problem so we can
announce a solution along with the vulnerability.
Package: django-tastypie-crust
Tastypie CrustYour Tastypie just become even tastier.RationaleThis package is really just a collection of snippets I use constantly with
Tastypie across multiple projects. They are reused so much it just makes more
sense to collect them together than copy-pasting codes everywhere.None of the snippets in this package originate from myself. The idea of
“resource actions”, in particular, came fromtastypie-actionsby Justin
Alexander (akathelonecabbageon GitHub), although I re-implemented the
details quite a bit. Some other utilities are mostly collected from snippets
floating around the Internet (StackOverflow,djangosnippets.org, etc.).ComponentsResourcesclass ActionResourceMixinResources subclassing this mixin can have methods decorated withaction,
making those methods accessible throught Tastypie API.action(name=None, url=None, static=False,
       allowed=None, login_required=False, throttled=False)Decorator that makes extra resource methods accessible through Tastypie API.Authenticationclass AnonymousAuthenticationAuthentication policy that only allows certain request methods go through
anonymously.ExampleSome example usages can be found insidetestproj/testapp/resources.py.LicenseBSD 3-cluse license. See fileLICENSEfor its content.ContributingTo run tests in this project, you needdjango-noseandcoveragealong
with obvious dependencies. Runpython testproj/manage.py testin the
project root to invoke tests.
Package: django-tastypie-elasticsearch
django-tastypie-elasticsearch=============================ElasticSearch support for django-tastypieInstallation------------```$ pip install django-tastypie-elasticsearch```Requirements------------* Python_ 2.7+ (not tested with lower version)* Django_ 1.4+ (may work on lower version, but not tested)* django-tastypie_ 0.9.11+* elasticsearch official python module.. _Python: https://python.org.. _Django: http://djangoproject.com.. _django-tastypie: http://tastypieapi.org.. _ElasticSearch: http://elasticsearch.orgHow to use?-----------* See documentation: http://django-tastypie-elasticsearch.readthedocs.org* Mailing list: https://groups.google.com/forum/?fromgroups#!forum/django-tastypie-elasticsearch
Package: django-tastypie-extras
A set of Django Tastypie extras.Table of contentsResourcesMultipartResourceMixinReadOnlyResourceMixinPaginatorSmartPaginatorAuthenticationSwaggerApiKeyAuthenticationResourcesMultipartResourceMixinResource with upload image possibilityReadOnlyResourceMixinRaiseBadRequestonupdate,createordeleterequest.PaginatorSmartPaginatorSmartPaginatordoes not performSELECTCOUNT(*)whenlimitis 0 andoffsetis 0limitis greater than 0 andoffsetis 0 and length ofself.objectsis lower thanlimitAuthenticationSwaggerApiKeyAuthenticationSwaggerUIprovides request authentication only throughapi_keyparameter.SwaggerApiKeyAuthenticationreadsusernameandapi_keyfromapi_keyrequest parameter.
Package: django-tastypie-legacy
Creating delicious APIs for Django apps since 2010.Currently in beta (v0.12.2) but being used actively in production on several
sites.RequirementsCorePython 2.6+ or Python 3.3+Django 1.5 through Django 1.8dateutil (http://labix.org/python-dateutil) >= 2.1Format SupportXML: lxml 3 (http://lxml.de/) and defusedxml (https://pypi.python.org/pypi/defusedxml)YAML: pyyaml (http://pyyaml.org/)binary plist: biplist (http://explorapp.com/biplist/)OptionalHTTP Digest authentication: python3-digest (https://bitbucket.org/akoha/python-digest/)What’s It Look Like?A basic example looks like:# myapp/api.py# ============fromtastypie.resourcesimportModelResourcefrommyapp.modelsimportEntryclassEntryResource(ModelResource):classMeta:queryset=Entry.objects.all()# urls.py# =======fromdjango.conf.urls.defaultsimport*fromtastypie.apiimportApifrommyapp.apiimportEntryResourcev1_api=Api(api_name='v1')v1_api.register(EntryResource())urlpatterns=patterns('',# The normal jazz here then...(r'^api/',include(v1_api.urls)),)That gets you a fully working, read-write API for theEntrymodel that
supports all CRUD operations in a RESTful way. JSON/XML/YAML support is already
there, and it’s easy to add related data/authentication/caching.You can find more in the documentation athttp://django-tastypie.readthedocs.org/.Why Tastypie?There are other, better known API frameworks out there for Django. You need to
assess the options available and decide for yourself. That said, here are some
common reasons for tastypie.You need an API that is RESTful and uses HTTP well.You want to support deep relations.You DON’T want to have to write your own serializer to make the output right.You want an API framework that has little magic, very flexible and maps well to
the problem domain.You want/need XML serialization that is treated equally to JSON (and YAML is
there too).You want to support my perceived NIH syndrome, which is less about NIH and more
about trying to help out friends/coworkers.Reference Materialhttp://github.com/toastdriven/django-tastypie/tree/master/tests/basicshows
basic usage of tastypiehttp://en.wikipedia.org/wiki/RESThttp://en.wikipedia.org/wiki/List_of_HTTP_status_codeshttp://www.ietf.org/rfc/rfc2616.txthttp://jacobian.org/writing/rest-worst-practices/SecurityTastypie is committed to providing a flexible and secure API, and was designed
with many security features and options in mind. Due to the complex nature of
APIs and the constant discovery of new attack vectors and vulnerabilities,
no software is immune to security holes. We rely on our community to report
and help us investigate security issues.If you come across a security holeplease do not open a Github issue.
Instead,drop us an emailattastypie-security@googlegroups.comWe’ll then work together to investigate and resolve the problem so we can
announce a solution along with the vulnerability.
Package: django-tastypie-migrate-fix
Creating delicious APIs for Django apps since 2010.Currently in beta (v0.9.14) but being used actively in production on several
sites.RequirementsCorePython 2.6+ or Python 3.3+Django 1.5+dateutil (http://labix.org/python-dateutil) >= 2.1Format SupportXML: lxml 3 (http://lxml.de/) and defusedxml (https://pypi.python.org/pypi/defusedxml)YAML: pyyaml (http://pyyaml.org/)binary plist: biplist (http://explorapp.com/biplist/)OptionalHTTP Digest authentication: python3-digest (https://bitbucket.org/akoha/python-digest/)What’s It Look Like?A basic example looks like:# myapp/api.py
# ============
from tastypie.resources import ModelResource
from myapp.models import Entry


class EntryResource(ModelResource):
    class Meta:
        queryset = Entry.objects.all()


# urls.py
# =======
from django.conf.urls.defaults import *
from tastypie.api import Api
from myapp.api import EntryResource

v1_api = Api(api_name='v1')
v1_api.register(EntryResource())

urlpatterns = patterns('',
    # The normal jazz here then...
    (r'^api/', include(v1_api.urls)),
)That gets you a fully working, read-write API for theEntrymodel that
supports all CRUD operations in a RESTful way. JSON/XML/YAML support is already
there, and it’s easy to add related data/authentication/caching.You can find more in the documentation athttp://django-tastypie.readthedocs.org/.Why Tastypie?There are other, better known API frameworks out there for Django. You need to
assess the options available and decide for yourself. That said, here are some
common reasons for tastypie.You need an API that is RESTful and uses HTTP well.You want to support deep relations.You DON’T want to have to write your own serializer to make the output right.You want an API framework that has little magic, very flexible and maps well to
the problem domain.You want/need XML serialization that is treated equally to JSON (and YAML is
there too).You want to support my perceived NIH syndrome, which is less about NIH and more
about trying to help out friends/coworkers.Reference Materialhttp://github.com/toastdriven/django-tastypie/tree/master/tests/basicshows
basic usage of tastypiehttp://en.wikipedia.org/wiki/RESThttp://en.wikipedia.org/wiki/List_of_HTTP_status_codeshttp://www.ietf.org/rfc/rfc2616.txthttp://jacobian.org/writing/rest-worst-practices/SecurityTastypie is committed to providing a flexible and secure API, and was designed
with many security features and options in mind. Due to the complex nature of
APIs and the constant discovery of new attack vectors and vulnerabilities,
no software is immune to security holes. We rely on our community to report
and help us investigate security issues.If you come across a security holeplease do not open a Github issue.
Instead,drop us an emailattastypie-security@googlegroups.comWe’ll then work together to investigate and resolve the problem so we can
announce a solution along with the vulnerability.
Package: django-tastypie-mongoengine
This Django application providesMongoEnginesupport fordjango-tastypie.RequirementsPython2.6+Django1.5+django-tastypie0.9.12+MongoEngine>0.8.0, <0.8.2How to use?See documentation:http://django-tastypie-mongoengine.readthedocs.orgSee usage in tests:http://github.com/wlanslovenija/django-tastypie-mongoengine/tree/master/tests
Package: django-tastypie-ng
Creating delicious APIs for Django apps since 2010.Currently in beta but being used actively in production on several
sites.RequirementsCorePython 3.6+, preferably 3.8+ (Whatever is supported by your version of Django)Django 2.2, 3.2 (LTS releases), 4.0, or Django 4.1 (latest release)dateutil (http://labix.org/python-dateutil) >= 2.1Format SupportXML: lxml 3 (http://lxml.de/) and defusedxml (https://pypi.python.org/pypi/defusedxml)YAML: pyyaml (http://pyyaml.org/)binary plist: biplist (https://bitbucket.org/wooster/biplist)OptionalHTTP Digest authentication: python3-digest (https://bitbucket.org/akoha/python-digest/)What’s It Look Like?A basic example looks like:# myapp/api.py# ============fromtastypie.resourcesimportModelResourcefrommyapp.modelsimportEntryclassEntryResource(ModelResource):classMeta:queryset=Entry.objects.all()# urls.py# =======fromdjango.urls.confimportre_path,includefromtastypie.apiimportApifrommyapp.apiimportEntryResourcev1_api=Api(api_name='v1')v1_api.register(EntryResource())urlpatterns=[# The normal jazz here then...re_path(r'^api/',include(v1_api.urls)),]That gets you a fully working, read-write API for theEntrymodel that
supports all CRUD operations in a RESTful way. JSON/XML/YAML support is already
there, and it’s easy to add related data/authentication/caching.You can find more in the documentation athttps://django-tastypie.readthedocs.io/.Why Tastypie?There are other API frameworks out there for Django. You need to
assess the options available and decide for yourself. That said, here are some
common reasons for tastypie.You need an API that is RESTful and uses HTTP well.You want to support deep relations.You DON’T want to have to write your own serializer to make the output right.You want an API framework that has little magic, very flexible and maps well to
the problem domain.You want/need XML serialization that is treated equally to JSON (and YAML is
there too).Reference Materialhttps://django-tastypie.readthedocs.io/en/latest/https://github.com/django-tastypie/django-tastypie/tree/master/tests/basicshows
basic usage of tastypiehttp://en.wikipedia.org/wiki/RESThttp://en.wikipedia.org/wiki/List_of_HTTP_status_codeshttp://www.ietf.org/rfc/rfc2616.txthttp://jacobian.org/writing/rest-worst-practices/Getting HelpThere are two primary ways of getting help.Go toStackOverflowand post a question with thetastypietag.We have an IRC channel (#tastypie on irc.freenode.net) to get help,
bounce an idea by us, or generally shoot the breeze.SecurityTastypie is committed to providing a flexible and secure API, and was designed
with many security features and options in mind. Due to the complex nature of
APIs and the constant discovery of new attack vectors and vulnerabilities,
no software is immune to security holes. We rely on our community to report
and help us investigate security issues.If you come across a security holeplease do not open a Github issue.
Instead,drop us an emailattastypie-security@googlegroups.comWe’ll then work together to investigate and resolve the problem so we can
announce a solution along with the vulnerability.