Saravanan666/pypi-org huggingface dataset:
Package: django-appconf
A helper class for handling configuration defaults of packaged Django
apps gracefully.NoteThis app precedes Django’s ownAppConfigclasses that act as
“objects [to] store metadata for an application” inside Django’s
app loading mechanism. In other words, they solve a related but
different use case than django-appconf and can’t easily be used
as a replacement. The similarity in name is purely coincidental.OverviewSay you have an app calledmyappwith a few defaults, which you want
to refer to in the app’s code without repeating yourself all the time.appconfprovides a simple class to implement those defaults. Simply add
something like the following code somewhere in your app files:fromappconfimportAppConfclassMyAppConf(AppConf):SETTING_1="one"SETTING_2=("two",)NoteAppConfclasses depend on being imported during startup of the Django
process. Even though there are multiple modules loaded automatically,
only themodelsmodules (usually themodels.pyfile of your
app) are guaranteed to be loaded at startup. Therefore it’s recommended
to put yourAppConfsubclass(es) there, too.The settings are initialized with the capitalized app label of where the
setting is located at. E.g. if yourmodels.pywith theAppConfclass
is in themyapppackage, the prefix of the settings will beMYAPP.You can override the default prefix by specifying aprefixattribute of
an innerMetaclass:fromappconfimportAppConfclassAcmeAppConf(AppConf):SETTING_1="one"SETTING_2=("two",)classMeta:prefix='acme'TheMyAppConfclass will automatically look at Django’s global settings
to determine if you’ve overridden it. For example, adding this to your site’ssettings.pywould overrideSETTING_1of the aboveMyAppConf:ACME_SETTING_1="uno"Since django-appconf completes Django’s global settings with its default values
(like “one” above), the standardpython manage.py diffsettingswill show
these defaults automatically.In case you want to use a different settings object instead of the default'django.conf.settings', set theholderattribute of the innerMetaclass to a dotted import path:fromappconfimportAppConfclassMyAppConf(AppConf):SETTING_1="one"SETTING_2=("two",)classMeta:prefix='acme'holder='acme.conf.settings'If you ship anAppConfclass with your reusable Django app, it’s
recommended to put it in aconf.pyfile of your app package and
importdjango.conf.settingsin it, too:fromdjango.confimportsettingsfromappconfimportAppConfclassMyAppConf(AppConf):SETTING_1="one"SETTING_2=("two",)In the other files of your app you can easily make sure the settings
are correctly loaded if you import Django’s settings object from that
module, e.g. in your app’sviews.py:fromdjango.httpimportHttpResponsefrommyapp.confimportsettingsdefindex(request):text='Setting 1 is:%s'%settings.MYAPP_SETTING_1returnHttpResponse(text)
Package: django-appcore
django-appcoredjango-appcoreis a reusable useful tools for Django 1.7+ application programming.Requirementsdjango >= 1.7
django-appconf>=0.6InstallationDownload and installdjango-appcoreusingoneof the following methods:PIPYou can install the latest stable package running this command:$ pip install django-appcoreAlso you can install the development version running this command:$ pip install -e git+http://github.com/dlancer/django-appcore.git#egg=appcore-devSetuptoolsYou can install the latest stable package running:$ easy_install django-appcoreUsageYou may find detailed documentation in the “docs” directory.
Package: django-app-enabler
DescriptionPoC autoconfigurator for django applicationsdjango-app-enablergoal is to reduce the configuration of a django application to a
one command operation to ease using django applications, both for newcomers and expert developers.As configuring a django application can be both boring (as 90% are the usual steps editingsettings.pyandurls.py)
and complex (as it’s easy to overlook one vital configuration parameter), replacing this with a single command sounds like
a real benefit.Key pointszero-knowledge tool to enable and configure django applications in a django projectrely on specification file shipped by the target application to patch django project configurationnot a replacement for existing package or dependencies managers (pip / poetry / pipenv / …)CaveatsProject is currently just a proof of conceptNo formal specification or documentation exist (yet) for addon configuration fileA lot of restrictions regarding thesettings.pyandurls.pyfiles are currently in placeNot all standard django settings options are currently supportedSeeusagefor more details.Compatible packagesUp-to-date list of compatible packagesHistory0.3.0 (2023-11-09)FeaturesImprove merge strategy to support all the basic standard Django settings (#5)Add support for external configuration json (#9)Upgrade to Django 3.2/4.2 (#32)Switch to Coveralls Github action (#56)Migrate to bump-my-version (#58)0.2.0 (2020-12-27)FeaturesAdd CLI utility (#20)BugfixesClose resource_stream file pointer (#19)Fix importing include multiple times in urlconf (#21)Add test to verify no multiple urlconf are added (#25)0.1.1 (2020-12-21)FeaturesAdd codeql action (#15)BugfixesFix errors with urlconf patching (#17)0.1.0 (2020-12-20)Initial releaseFeaturesAdd install command (#1)Add tests (#2)Add support for message addon config parameter (#11)Improved DocumentationImprove documentation (#1)
Package: djangoappengine
Documentation athttp://djangoappengine.readthedocs.org/Djangoappengine allows you to use App Engine’s datastore with
Django. It provides the necessary plumbing to query the datastore, and
custom management commands for deploying and running the SDK.master:ContributingYou are highly encouraged to participate in the development, simply use
GitHub’s fork/pull request system.If you don’t like GitHub (for some reason) you’re welcome
to send regular patches to the mailing list.Mailing list:http://groups.google.com/group/django-non-relationalBug tracker:https://github.com/django-nonrel/djangoappengine/issuesLicense:3-clause BSD, see LICENSEKeywords:django, app engine, orm, nosql, database, python
Package: django-appengine-auth
Remote Google App Engine OAuth backend for Django=================================================[Django-AppEngine-Auth](https://github.com/mback2k/django-appengine-auth) is anextension to [Django-Social-Auth](https://github.com/omab/django-social-auth)which adds a OAuth backend for Google App Engine based Google Accounts.This application makes use of the[Google App Engine OAuth Profile endpoint application](https://github.com/mback2k/appengine-oauth-profile)which is by default hosted at https://oauth-profile.appspot.com/Dependencies------------- django-social-auth [https://github.com/omab/django-social-auth]- oauth2             [https://github.com/simplegeo/python-oauth2]Installation------------Install the latest version from pypi.python.org:pip install django-appengine-authInstall the development version by cloning the source from github.com:pip install git+https://github.com/mback2k/django-appengine-auth.gitConfiguration-------------Add the package to your `INSTALLED_APPS`:INSTALLED_APPS += ('social_auth','appengine_auth',)Add the desired backends to your `AUTHENTICATION BACKENDS`:AUTHENTICATION_BACKENDS += ('appengine_auth.backends.GoogleAppEngineOAuthBackend','appengine_auth.backends.GoogleAppEngineOAuth2Backend',)Add the pipeline to your `SOCIAL_AUTH_PIPELINE`:SOCIAL_AUTH_PIPELINE = ('social_auth.backends.pipeline.social.social_auth_user','appengine_auth.pipelines.associate_by_user_id',# Removed by default since it can be a dangerouse behavior that# could lead to accounts take over.#'social_auth.backends.pipeline.associate.associate_by_email','social_auth.backends.pipeline.user.get_username','social_auth.backends.pipeline.user.create_user','social_auth.backends.pipeline.social.associate_user','social_auth.backends.pipeline.social.load_extra_data','social_auth.backends.pipeline.user.update_user_details',)Additional Settings-------------------Add some or all of the following settings to your `settings.py`:# Hostname of the OAuth and Web Service endpointGOOGLE_APPENGINE_OAUTH_SERVER = 'oauth-profile.appspot.com'# Use static and unique Google App Engine user's user_id as identifier# Defaults to False which makes it use the user's email addressGOOGLE_APPENGINE_OAUTH_USE_UNIQUE_USER_ID = True# Setup Google OAuth 1.0 consumer key and secretGOOGLE_APPENGINE_CONSUMER_KEY = ''GOOGLE_APPENGINE_CONSUMER_SECRET = ''# or Setup Google OAuth 2.0 client id and secretGOOGLE_APPENGINE_CLIENT_ID = ''GOOGLE_APPENGINE_CLIENT_SECRET = ''Please refer to the [Django-Social-Auth](http://django-social-auth.readthedocs.org/)documentation for additional information.License-------* Released under MIT License* Copyright (c) 2012-2015 Marc Hoersken <info@marc-hoersken.de>
Package: django-appengine-toolkit
Appengine Toolkit pimps Django with some utilities that help deploying
projects on Google App Engine with Google Cloud SQL as data backend.Featurescollects project dependencies symlinking needed modules and packages and configuring App Engine environmentconfigures DATABASE setting parsing connection strings similar to those on Herokuprovides a custom storage for Google Cloud StorageDocumentationThe full documentation is athttp://django-appengine-toolkit.rtfd.org.A tutorial was published onGoogle Developers BlogAppEngine SDK version supported: 1.9.2QuickstartInstall appengine-toolkit:pip install django-appengine-toolkitAdd it to the installed apps:INSTALLED_APPS = (
    # ...
    'appengine_toolkit',
)To automatically configure database settings by parsing connection string
contained in DATABASE_URL enviroment var:import appengine_toolkit
DATABASES = {
    'default': appengine_toolkit.config(),
}You can set DATABASE_URL directly in yourapp.yamlfile:env_variables:
  DJANGO_SETTINGS_MODULE: 'myapp.settings'
  DATABASE_URL: 'mysql://root@project_id:instance_id/database_name'To collect project dependencies, first configure Appengine Toolkit in your settings
file, specifying the full path to your app.yaml file:APPENGINE_TOOLKIT = {
    'APP_YAML': os.path.join(BASE_DIR, '../../', 'app.yaml'),
}…then run the commandcollectdepsspecifying the requirement file containing
the list of packages needed by your project to run:python manage.py collectdeps -r my_requirements.txta folder namedlibswill be created on your application root (i.e. the same folder
where the YAML file resides) containing symlinks needed by App Engine to include
dependencies in the production runtime enviroment.A fileappengine_config.pywill be created in the same folder and will contain
code needed to configure the environment. If you need to customize the moduleappengine_configtell the command to not overwrite it - the command will then
output the code you need to paste inside the module to complete the configuration
processNeed to store your media files on Google Cloud Storage? Just add this to your settings:APPENGINE_TOOLKIT = {
    # ...,
    'BUCKET_NAME': 'your-bucket-name',
}
DEFAULT_FILE_STORAGE = 'appengine_toolkit.storage.GoogleCloudStorage'History0.2.0 (2014-01-09)Fixed setup requirements for GCS libraryApp Engine SDK 1.9 compatibility0.2.0 (2014-01-09)Added support for Google Cloud Storage0.1.2 (2013-12-04)Fixed setup script0.1.1 (2013-12-04)Finished first draft of docs0.1.0 (2013-11-30)First release on PyPI.
Package: django-app-graphql
IntroductionDjango app that expose a graphql schema as well as a graphiql interface.UserInstallationpip install django-app-graphqlConfigurationinINSTALLED_APPSyou need to add:'graphene_django',
'django_filters',After all your apps you need to use this app(this is important otherwise some models won’t be detected at all!):'django_app_graphql',The first thing you need to do is determine if you want your graphql server setupped
usinggrapheneor usingariadne. In settings, write:DJANGOAPPGRAPHQL = dict(
    BACKENDTYPE="ariadne/graphene"
)and select eitherariadneorgraphene.Finally, inurls.pyof the entire project add the following line:urlpatterns = [
    ...
    path("graphqls/", include("django_app_graphql.urls")),
    ...
]You have chosen grapheneThe app needs to be deploy for last because otherwise it cannot detect all the Django models and their types.
You also need to configure the authentication proces. Hence you need t add “AUTHENTICATION_BACKENDS” in thesettings.py:AUTHENTICATION_BACKENDS = [
    "graphql_jwt.backends.JSONWebTokenBackend",
    "django.contrib.auth.backends.ModelBackend"
]After that, you need to properly configure the graphene, graphenedjango-extras and graphene-jwt. Add all these in yoursettings.py:GRAPHENE = dict(
    SCHEMA" = "django_app_graphql.graphene.schema.SCHEMA",
    SCHEMA_OUTPUT = 'graphql-schema.json',
    SCHEMA_INDENT = 2,
    MIDDLEWARE = [
        "graphql_jwt.middleware.JSONWebTokenMiddleware",
        "django_app_graphql.middleware.GraphQLStackTraceInErrorMiddleware",
    ],
)

GRAPHENE_DJANGO_EXTRAS = dict(
    DEFAULT_PAGINATION_CLASS = 'graphene_django_extras.paginations.LimitOffsetGraphqlPagination',
    DEFAULT_PAGE_SIZE = 20,
    MAX_PAGE_SIZE = 50,
    CACHE_ACTIVE = True,
    CACHE_TIMEOUT = 300  # seconds
)

# see https://django-graphql-jwt.domake.io/en/latest/refresh_token.html
GRAPHQL_JWT = dict(
    # This configures graphql-jwt to add "token" input at each request to be authenticated
    JWT_ALLOW_ARGUMENT = True,
    JWT_ARGUMENT_NAME = "token",
    JWT_VERIFY_EXPIRATION = True,
    JWT_EXPIRATION_DELTA = timedelta(minutes=30),
    JWT_ALGORITHM = "HS256",
    JWT_REFRESH_EXPIRATION_DELTA = timedelta(days=7),
    JWT_AUTH_HEADER_PREFIX = "Bearer",
)You have chosen ariadneInsettings.pyadd:INSTALLED_APPS = [
    ...
    "ariadne.contrib.django",
]Add templates (otherwise the playground won’t work):TEMPLATES = [
    {
        ...,
        'APP_DIRS': True,
        ...
    },
]Ariadne is in unstable development (I don’t know if it will ever be supported)Generic tweaksFinally you can configure this app, for instance:DJANGO_APP_GRAPHQL = {
    "BACKEND_TYPE": "graphene",
    "EXPOSE_GRAPHIQL": True,
    "GRAPHQL_SERVER_URL": "",
    "ENABLE_GRAPHQL_FEDERATION": True,
    "SAVE_GRAPHQL_SCHEMA": "output/schema.graphql"
}DeveloperUpdate new version (only for developers)You can usesetuptoolsandtwine:python setup.py update_version_patch bdist_wheel
twine upload dist/*Or you can usepmakeuppmakeup update-version-patch build upload-to-pypi
Package: django-applepodcast
Django Apple PodcastDjango Apple Podcastis aDjangopodcastapplicationoptimized forApple Podcasts. FormerlyDjango iTunes Podcast.Package distributionCode repositoryDocumentationTestsAn online demo also exists.Online demoOnline demo code repositoryInstall$pipenvinstalldjango-applepodcastAdd tosettings.py.INSTALLED_APPS=[# ...'podcast',]Add tourls.py.fromdjango.urlsimportinclude,pathurlpatterns=[# ...path('podcast/',include('podcast.urls')),]Migrate the database.$pipenvrunpythonmanage.pymigrateLoad the fixtures.$pipenvrunpythonmanage.pyloaddatapodcast_category.jsonUsageRun the local server.$pipenvrunpythonmanage.pyrunserverVisit either the show view or the admin.http://127.0.0.1:8000/podcast/http://127.0.0.1:8000/admin/podcast/
Package: django-appmedia
the intention of this application is to enable static app files (css, js, pics) in the app folder itself.<application1>/media/<application1>/js/script.js
<application2>/media/<application2>/js/script.js<project>/media/logo.jpgTo use this view in development you should add something like the following to urls.py:
if settings.DEBUG: urlpatterns += (r’^media/(?P<path>.*)$’, ‘site.media.serve_apps’, {‘document_root’ : settings.MEDIA_ROOT})For deployment there is a managament command calledsymlinkmediathat will create symlinks to each applications media directory inMEDIA_ROOT.Now all apps in INSTALLED_APPS that have a “media” directory in them will be reachable as ‘/media/<application_name>/’.You can then have the admin media files served by setting ADMIN_MEDIA_PREFIX = ‘/media/admin/’
Package: django-app-novadata
django_app_novadataDjango App novadata PyPI package.Getting StartedO objetivo desse pacote, é automatizar o retrabalho de tarefas com django.
Dessa forma é possível aplicar em diversos outros projetos com apenas poucos comandos no terminal.DependenciesVocê precisa do Python 3.6 or superior para usarpacotepypi. você pode encontrar empython.org.
Você também precisa de setuptools, pacotes de wheel e twine, que estão disponíveis emPyPI. Em seu pip, basta executar:pip install setuptools
pip install wheel
pip install twineInstallationEsse pacote está disponível Python Package Index (PyPI):pip install django-app-novadataAdicione os seguintes trechos de códigos em seu arquivo settings.py:2.1 Adicione o pacote na variavel INSTALLED_APPS como PRIMEIRA OPÇÃO!# Definição das apps
INSTALLED_APPS = [
    'django_app_novadata',
    ...
]2.2 Variaveis utilizadas na autenticação do pacote.LOGIN_URL = '/login/'
LOGIN_REDIRECT_URL = '/'Abra o terminal e aplique os seguintes comandos para adicionar as migrações e arquivos estaticos da nova App:Migração:python manage.py migrateArquivos Estáticos:python manage.py collectstaticPor fim, adicione as urls do pacote no url.py na da app principal:urlpatterns = [
    path('admin/', admin.site.urls),
    path('', include('django_app_novadata.urls')),
]
Package: django-appointment-ds
django-appointment_dsdjango-appointment_ds is a Django app to use for demiansoft.Quick startAdd "appointment" to your INSTALLED_APPS setting like thisINSTALLED_APPS=[...'appointment',]코드를 넣고자 하는 위치에 다음을 추가 한다.{% load appointment_tags %}
{% make_appointment %}post 메시지 처리를 위한 make_post_context 함수를 사용한다.(테마 앱의 views.py 안의 buildup 함수에 추가한다.)fromappointment.templatetags.appointment_tagsimportmake_post_context...ifrequest.method=='GET':returnrender(request,f"mentor_ds/base.html",context)elifrequest.method=="POST":context.update(make_post_context(request.POST,context['basic_info']['consult_email']))returnrender(request,f"mentor_ds/base.html",context)context examplecontext={"color":"default","theme":"mentor_ds","naver":"https://booking.naver.com/booking/13/bizes/441781",# None으로 설정시 버튼 안보임'basic_info':{'consult_email':'hj3415@gmail.com'}}Required vendor - jquerycontact 에 포함된 appointment 폼을 추출하는 경우 - 따로 appointment 섹션이 없기 때문에 css 파일과 html 파일의 contact 에서 php-email-form 파트를
추출 하여 .contact 을 .appointment 로 .php-email-form 을 .email-form 으로 일괄 변환 한다.
Package: django-appointments
Django AppointmentsDjango Appointments is a Django reusable app for managing hospitals, doctor’s & patients.
This Package comes with build in admin panel to manage users & hospitals.
Hospitals can manage doctors, confirm appointments, view appointments.
Pateints can sign up and create their profile to book appointments.
Once appointment is confirmed appointment date and time is mailed to Doctor and Patient.
Users can also regenrate passwords by password reset link.Quick startAdd “crispy_forms”,”doctor”, “hospital”, “patient” & “user” to your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'crispy_forms',
    'doctor',
    'hospital',
    'patient',
    'user',
    ...
]Add line : AUTH_USER_MODEL=’user.CustomUser’  to setting.pyInclude the app URLconf in your project urls.py like this:path('', include('user.urls')),Add SMTP server details to settings.py:-EMAIL_BACKEND =’django.core.mail.backends.smtp.EmailBackend’
EMAIL_HOST = ‘smtp.your-host.com’
EMAIL_USE_TLS = True
EMAIL_PORT = 587
EMAIL_HOST_USER =‘user@your-host.com’
EMAIL_HOST_PASSWORD = ‘your-password’Runpython manage.py makemigrationsto create the migrations.Runpython manage.py migrateto create the app models.Runpython manage.py createsuperuserto create admin username & password to login.Start the development server and visithttp://127.0.0.1:8000/manage/to manage files & settings.Visithttp://127.0.0.1:8000/admin/to add hospitals.Hospital can add doctors.Visithttp://127.0.0.1:8000/signup/to for patient signup.Visithttp://127.0.0.1:8000/login/to login for doctors, hospitals, patients.PyPI page:https://pypi.org/project/django-appointments/Bugtracker:https://github.com/deligence-vinit/django-appointments/issuesCode repository:https://github.com/deligence-vinit/django-appointmentsFor integration contactsanjay@deligence.com
Package: django-app-plugins
A template extension system for marking points in your django templates as
‘plugin-points’, and providing plugins which inject themselves at those points.
Multiple applications can be injected at each plugin point, and ‘registered’
plugin-points can have the visibility, order and access of the plugins
controlled via DB models. This control can be done on a site wide or per-user
basis. Thus you can allow users to add, remove, and reorder the plugins on their
profile page for instance.
Package: django-appregister
Django appregisterDjango appregister is a building blocks app to implement a class registry
system for your django app. It uses a similar approach to the Django admin,
allowing you to register classes and supports an autodiscover feature.A registry system that provides a good base for making an app plugable and
extendable by third parties as they can register their own subclasses for
Use within the main code base.InstallationUse pip:pip install django-appregisterQuick Example UsageFirst, you should create your base class that all registered classes must be a
subclass of. Often this is a base Model class in your models.py or it can be
anywhere in your project:>>> class AppPlugin(object):
...     passThen you need to create your own registry, the base can either be a class, or a
dotted string that points to the base class, such as"myapp.AppPlugin".
After that, you can go ahead and create an instance of the registry - creating
it at the module level makes it easy to re-use across the project but you can
have as many instances as you need. It’s good practice to create your registry
in its own module, such asmyapp/register.py:>>> from appregister import Registry

>>> class MyRegistry(Registry):
...     base = AppPlugin
...     discovermodule = 'plugins'

>>> plugins = MyRegistry()Now that you have the registry, you can start to add subclasses to it. This can
be done by using the class decorator on your register:>>> @plugins.register
... class MyPlugin(AppPlugin):
...     passNote, If you are using version 2.5 or below of Python you can’t use the class
based decorator, you will need to call it manually. The above example would
then become:>>> class MySecondPlugin(AppPlugin):
...     pass
>>> plugins.register(MySecondPlugin)
<class 'MySecondPlugin'>Registering an invalid object will raise an InvalidOperation exception:>>> # Note that this class does not inherit from the base we specified.
>>> class MyNonSubclass(object):
...     pass

>>> plugins.register(MyNonSubclass)
Traceback (most recent call last):
    ...
InvalidOperation: Object 'MyNonSubclass' is not a subclass of 'AppPlugin'Finally, now you can get all your objects back - this includes those registered
by a third party:>>> len(plugins)
2

>>> for plugin in plugins:
...     print plugin
<class 'MySecondPlugin'>
<class 'MyPlugin'>The order of registration is not stored. Since we can’t tell what order they
would be registered, if you want a sorted set you will need to sort them
after they have all been registered:>>> plugins.clear()
>>> len(plugins)
0