Saravanan666/pypi-org huggingface dataset:
Package: django-oscar-unicredit
===================================Unicredit package for django-oscar===================================This package provides integration between django-oscar_ and `Unicredit`_... _django-oscar: https://github.com/tangentlabs/django-oscarSupport-------Having problems or got a question?* write to me an email info@marcominutoli.it---------------Getting started---------------Add 'unicredit' in your INSTALLED_APPS::Add the following settings using the details from your sandbox buyer account::UNICREDIT_ID_ESERCENTE = 'XXXXXX'UNICREDIT_STABILIMENTO = 'XXXXX'UNICREDIT_USERID = 'XXXXX'UNICREDIT_PASSWORD = 'XXXXXX'UNICREDIT_STRINGA_SICUREZZA = 'XXXXXXXX'Next, you need to add the Unicredit URLs to your URL config.  This can be done asfollows::from django.contrib import adminfrom oscar.app import shopurlpatterns = patterns('',(r'^admin/', include(admin.site.urls)),(r'^checkout/unicredit/', include('unicredit.urls')),(r'', include(shop.urls)),To insert the UNICREDIT button in your template ``templates/oscar/checkout/preview.html`` aggiungendo::<form method="post" action="{% url 'unicredit-direct-payment' %}" id="place-order-form-unicredit">{% csrf_token %}<input type="hidden" name="action" value="place_order"/><div class="form-actions"><button id='place-order' type="submit" class="pull-right btn btn-primary btn-large js-disable-on-click"data-loading-text="{% trans 'Submitting...' %}">Paga con unicredit</button></div></form>
Package: django-oscar-vat_moss
Enables EU VATMOSS processing for the Oscar e-commerce systemThis package enables e-commerce application based on Django Oscar to
assess and charge VAT (Value Added Tax) according to EU regulations.It is based ondjango-oscarandvat_moss-python.InstallationFor now, install withpip install https://github.com/hastexo/django-oscar-vat_moss/archive/master.zipto get the latest master. There are no named releases yet, and the
package isn’t yet on PyPI.UseTo use, you mustEnable a pricingStrategythat uses theDeferredTaxtax mixinAdd aCheckoutSessionMixinto your checkout session, so taxes can
be applied when the customer’s shipping address is knownOptionally extend your data model with a field accommodating your
customer’s VATIN (VAT Identification Number) if you want to enable
VAT-free B2B transactions under the reverse charge system. If all
your transactions are B2C, this last bit may be safely omitted.Enabling a VAT-enabled pricing strategyAddoscar_vat_moss.partner.strategy.VATStrategyto yourpartner/strategy.pymodule, and update yourSelectorto use it
when appropriate:# partner/strategy.pyfromoscar_vat_moss.partner.strategyimportVATStrategyclassSelector(object):defstrategy(self,request=None,user=None,**kwargs):# Apply your strategy selection logic, where appropriate:returnVATStrategy(request)If you only want one selector and youalwayswant to applyVATStrategy, you may also simply use:# partner/strategy.pyfromoscar_vat_moss.partner.strategyimport*Applying VAT on checkoutAddoscar_vat_moss.checkout.session.CheckoutSessionMixinto yourcheckout/session.pymodule:# checkout/session.pyfromoscar_vat_moss.checkout.sessionimportCheckoutSessionMixin
Package: django-oscar-wagtail
This project integrates the Wagtail CMS with Django Oscar for eCommerce. It
adds the following features:each Oscar category page can now be managed by the Wagtail CMSit is possible to add product lists to wagtail pagesInstallationPresuming you have installed Django-Oscar and Wagtail into your Django project.First install django-oscar-wagtail via PIP:pipinstalldjango-oscar-wagtailAnd addoscar_wagtailto your settings as follows:INSTALLED_APPS=[# ... your other apps'oscar_wagtail',]Add the URLs tourls.py:importoscar_wagtail.urlsurlpatterns+=[url(r'^api/oscar_wagtail/',include(oscar_wagtail.urls,namespace='oscar_wagtail')),]Fork the catalogue app as described in theoscar documentation. Then instead of
using the AbstractCategory from Oscar use the one from this project as follows:fromoscar_wagtail.abstract_modelsimportAbstractCategoryclassCategory(AbstractCategory):passfromoscar.apps.catalogue.modelsimport*If you want to have a CMS button in the Oscar dashboard, add the following to your settings:OSCAR_DASHBOARD_NAVIGATION.insert(1,{'label':'CMS','icon':'icon-th-list','url_name':'wagtailadmin_home','access_fn':lambdauser,*args:user.has_perm('wagtailadmin.access_admin')})
Package: django-oscar-webpay
Right now only theNORMALpayment method is available.This django app provides the necessary views and functionality for
integrate a WSDL WebPay payment service into adjango-oscar based site.This package has been only tested against the chilean WebPay
service.Important notes about payment flowOperation InitTransaction:Initializes a transaction in Webpay. In
response to the invocation, a Token is generated, which uniquely
represents a transaction. It is important to consider that once this
method is invoked, the delivered Token has a reduced life span of5 minutes, after which the Token is expired and can not be used
in a payment.Operation getTransactionResult:Corresponds to the operation after
the init Transaction. Allows you to obtain the result of the
transaction once Webpay has resolved your financial authorizationOperation acknowledgeTransaction:If the invocation is not
performed within 30 seconds (regardless of the result delivered by
the getTransactionResult method), Webpay will reverse the
transaction, assuming that the trade was unable to report its
result, thus preventing cardholder payment.ReferenceSettingsIn order to use this you must provide some configurations, you can setup
the methods you want to use, the methods are:NORMAL,NORMAL_MALL,CAPTUREorONECLICK.# Configuration exampleWEBPAY_RETURN_IP_ADDRESS='127.0.0.1'# Ip address of the host hosting the e-commerce site.WEBPAY_RETURN_PORT=8000# Port where the server is listening for?WEBPAY_NORMAL={'ACTIVE_ENVIRON':'INTEGRATION',# INTEGRATION, PRODUCTION or CERTIFICATION# This values determines which url is used# from the 'ENVIRONMENTS' setting.'ENVIRONMENTS':{# Map the service urls to the active environment value.'INTEGRATION':'https://webpay3gint.transbank.cl/WSWebpayTransaction/cxf/WSWebpayService?wsdl','CERTIFICATION':'https://webpay3gint.transbank.cl/WSWebpayTransaction/cxf/WSWebpayService?wsdl','PRODUCTION':'https://webpay3g.transbank.cl/WSWebpayTransaction/cxf/WSWebpayService?wsdl',},# The following settings are self explanatory.'PRIVATE_KEY':'~/webpay_dev_certs/integracion_normal/597020000541.key','PUBLIC_CERT':'~/webpay_dev_certs/integracion_normal/597020000541.crt','WEBPAY_CERT':'~/webpay_dev_certs/integracion_normal/tbk.pem','COMMERCE_CODE':'597020000541'}Redirecting toWebpayPaymentDetailsViewAdd the following:ifpayment_method.lower()=='webpay':returnredirect('webpay-redirect')to thePaymentDetailsView.getmethod.Including urlsAdd to your urls configuration:url(r'^checkout/',include('oscar_webpay.urls')),url(r'^dashboard/webpay/',include(webpay_dashboard.urls))Modifying dependenciesIf you are experiencing some problems getting this to work properly, try
to modify some dependencies according to this:TransbankDevelopers
Package: django-os-geocoder
This is a Django app that lets you load Ordnance Survey data and use it to find places.A list ofPlacesfrom the Ordnance Survey is stored in a spatial database, and a url is provided to query them by name and return a JSON response containing matching places. Useful for autocompleting inputs that take town, city or road names.In addition, the places are filtered by a series of bounding boxes, so that only places within the supplied boxes are returned.PrerequisitesA GeoDjango (https://docs.djangoproject.com/en/dev/ref/contrib/gis/tutorial/#introduction) project (Note, this has only been tested with Django 1.4.5 and a PostGIS database)InstallationAddgeocoderto yourINSTALLED_APPSlist in settings.pyImport the geocoder ajax url into your project’s urls.pySetGEOCODER_BOUNDING_BOXESto include one or more bounding boxesRunpython manage.py syncdbRestart your web server, if necessary.Datahttp://www.ordnancesurvey.co.uk/oswebsite/products/os-opendata.htmlThe Ordnance Survey make large data sets available under an open license. See the url above for more details. This app uses the OS Locator and 1:50k Gazetteer.Importing dataDownload the data from the Ordnance Survey website.Set theGEOCODER_BOUNDING_BOXESentry in yoursettings.py.Import the data using one of the import management commands, the path to the data file is the only argument.LicensingAnywhere you make use of the data from the OS you should display the following text:> Contains Ordnance Survey data © Crown copyright and database right 2013See the OS OpenData Licensing:http://www.ordnancesurvey.co.uk/oswebsite/opendata/licensing.htmlfor more details.
Package: django-osm
Project Open Street Map managementDocumentationThe full documentation is athttps://django-osm.readthedocs.io.QuickstartInstall django-osm:pip install django-osmAdd it to yourINSTALLED_APPS:INSTALLED_APPS=(..."django.contrib.gis","django_celery_beat","rest_framework","rest_framework_gis","osm",...)DATABASE_ROUTERS=[...'osm.route_db.Default']DATABASES={...'osm':{'ENGINE':'django.contrib.gis.db.backends.postgis','HOST':'localhost','NAME':'geodjango',},}OSM_REPLICS=['osm']If there is OSM database replication, then add the connection parameters to us in the list of databases:DATABASES={...'osm_replica1':{'ENGINE':'django.contrib.gis.db.backends.postgis','HOST':'localhost','NAME':'geodjango',},}And complete the list of replicas OSM_REPLICS:OSM_REPLICS=['osm','osm_replica1']Add django-osm’s URL patterns:urlpatterns=[...path('osm/',include('osm.urls',namespace='osm')),...]Add DRF settings:REST_FRAMEWORK={"DEFAULT_AUTHENTICATION_CLASSES":("rest_framework.authentication.SessionAuthentication","rest_framework.authentication.TokenAuthentication",),"DEFAULT_PERMISSION_CLASSES":("rest_framework.permissions.IsAuthenticated",),'DEFAULT_PAGINATION_CLASS':'rest_framework.pagination.LimitOffsetPagination','PAGE_SIZE':25}FeaturesTODORunning TestsDoes the code actually work?source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ toxDevelopment commandspip install -r requirements_dev.txt
invoke -lCreditsTools used in rendering this package:Cookiecuttercookiecutter-djangopackageHistory0.1.0 (2021-01-16)First release on PyPI.
Package: django-oso
OsoWhat is Oso?Oso is a batteries-included framework for building authorization in your application.With Oso, you can:Model: Set up common permissions patterns like role-based access control (RBAC) and relationships using Oso’s built-in primitives. Extend them however you need with Oso’s declarative policy language, Polar.Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.”Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the Oso debugger or REPL to track down unexpected behavior.Oso offers libraries forNode.js,Python,Go,Rust,Ruby, andJava.Our latest creation Oso Cloud makes authorization across services as easy as oso.authorize(user, action, resource).Learn about it.DocumentationTo get up and running with Oso, try theGetting Started guide.Full documentation is available atdocs.osohq.com.Check outUse Casesto learn more about how teams are using Oso in production.To learn about authorization best practices (not specific to Oso), read theAuthorization Academyguides.Community & SupportIf you have any questions on Oso or authorization more generally, you can join our engineering team & hundreds of other developers using Oso in our community Slack:Share your storyWe'd love to hear about your use case and experience with Oso. Share your story in ourSuccess Stories issue.DevelopmentCoreOso's Rustcoreis developed againstRust's latest stable
release.Language librariesOso's language libraries can be developed without touching the Rust core, but
you will still need the Rust stable toolchain installed in order to build the
core.To build the WebAssembly core for the Node.js library, you will need to havewasm-packinstalled and available on your system PATH.Language requirementsTo work on a language library, you will need to meet the following version
requirements:Java: 11+Maven: 3.6+Node.js: 12.20.0+Yarn 1.22+Python: 3.7+Ruby: 2.4+Bundler 2.1.4+Rust: 1.46+Go: 1.14+Contributing & JobsSee:CONTRIBUTING.md.If you want to work on the Oso codebase full-time, visitour jobs page.LicenseSee:LICENSE.
Package: django-oss2-storage
Installing from PyPI is as easy as doing:pip install django-oss2-storageOnce that is done addstoragesto yourINSTALLED_APPSand setDEFAULT_FILE_STORAGEto the
backend of your choice. If, for example, you want to use the boto3 backend you would set:DEFAULT_FILE_STORAGE = 'oss2_storage.backends.Oss2MediaStorage'
Package: django-oss-storage-for-dj4.0
Django AliCloud OSS Storage
===django-oss-storageprovides a Django AliCloud OSS file storage.Features
===Django file storage for AliCloud OSSDjango static file storage for AliCloud OSSWorks in Python 2 & 3Installation
===Install:: code-block:: bash$ pip install django-oss-storageAdd'django_oss_storage'to yourINSTALLED_APPSsettingSet yourDEFAULT_FILE_STORAGEsetting to"django_oss_storage.backends.OssMediaStorage"Set yourSTATICFILES_STORAGEsetting to"django_oss_storage.backends.OssStaticStorage"Configure your AliCloud OSS settings (Refer below).Use the following settings for file storage.:: code-block:: bashSTATICFILES_STORAGE = ‘django_oss_storage.backends.OssStaticStorage’DEFAULT_FILE_STORAGE = ‘django_oss_storage.backends.OssMediaStorage’Authentication settings
===Use the following settings to authenticate with AliCloud OSS.:: code-block:: bash# AliCloud access key ID
OSS_ACCESS_KEY_ID = <Your Access Key ID># AliCloud access key secret
OSS_ACCESS_KEY_SECRET = <Your Access Key Secret>Storage settings
===For public or public-read buckets, storage urls will be bucket_name.endpoint/key formatFor private buckets, storage urls will be signed url. The expires time can be set by OSS_EXPIRE_TIME as environment variable or as Django settings. The default value for OSS_EXPIRE_TIME is 30 days.:: code-block:: bashOSS_EXPIRE_TIME = <Expire Time in Seconds>File storage settings
===Use the following settings to configure AliCloud OSS file storage.:: code-block:: bash# The name of the bucket to store files in
OSS_BUCKET_NAME = <Your bucket name># The URL of AliCloud OSS endpoint
# Referhttps://www.alibabacloud.com/help/zh/doc-detail/31837.htmfor OSS Region & Endpoint
OSS_ENDPOINT = <Your access endpoint># The default location for your files
MEDIA_URL = ‘/media/’Staticfiles storage settings
===All of the file storage settings are available for the staticfiles storage.:: code-block:: bash# The default location for your static files
STATIC_URL = ‘/static/’staticfiles provides command ‘collectstatic’. Run following command to collect all sub-folder ‘static’ of each app
and upload to STATIC_URL.:: code-block:: bash$ python manage.py collectstaticTesting
===First set the required AccessKeyId, AccessKeySecret, endpoint and bucket information for the test through environment variables (Do not use the bucket for the production environment).
Take the Linux system for example::: code-block:: bash$ export OSS_ACCESS_KEY_ID=<AccessKeyId>
$ export OSS_ACCESS_KEY_SECRET=<AccessKeySecret>
$ export OSS_BUCKET_NAME=<bucket>
$ export OSS_ENDPOINT=<endpoint>Support and announcements
===Downloads and bug tracking can be found at themain project website.License
===MIT.
Package: django-otlp-log-exporter
django otlp log exporter (handler)Collecting Logs using OpenTelemetryOpenTelemetry provides various receivers and processors for collecting first-party and third-party logs directly via OpenTelemetry Collector or via existing agents such as FluentBit so that minimal changes are required to move to OpenTelemetry for logs.Collecting legacy first-party Application LogsThere are two ways to collect logs from these applications.Via File or Stdout LogsHere, the logs of the application are directly collected by the OpenTelemetry receiver using collectors like filelog receiver and operators and processors to parse them into the OTel model.Direct to collector ( our handler is implemented based on this approach )In this approach you can modify your logging library that is used by the application to use the logging SDK provided by OpenTelemetry and directly forward the logs from the application to OpenTelemetry. This approach removes any need for agents/intermediary medium but loses the simplicity of having the log file locally.Our ApproachYou can directly send your application logs to your opentelementry collector with our log handler (which is finally delivered to backends like signoz.)Installationpipinstalldjango-otlp-log-exporterConfiguration (settings.py)OTLP_ENDPOINT=env('OTLP_ENDPOINT')# its endpoint of your opentelementry collector listen on, defult= http://localhost:4317OTLP_IS_SECURE=env('OTLP_IS_SECURE')# its bool, default= TrueOTLP_TAG=env('OTLP_TAG')# for seprate logs, default= localhost debugLOGGING={'version':1,'disable_existing_loggers':False,'handlers':{'directlogging':{'level':'WARNING','class':'otlp_exporter.handler.DirectWriteLoggingHandler',},},'loggers':{'root':{'handlers':['directlogging',],'level':'WARNING','propagate':True,},},}Links:Much of our documentation is based on signoz.io's descriptions.Thanks for the inspirations of other packages written, especiallyhttps://github.com/jayfk/django-fluentd. If you find a bug or have a question, you can contact me via the link belowmojtaba.akbari.221B@gmail.com.
Package: django-otp-provider
Django otp providerOTPTransport: SMS or EMAILAsync (celery)Custom SMS providersRequirementsPython >= 3.0Django >= 2.0CeleryPyJWTSchemapip install django-otp-providerCreate your custom class extends fromBaseTransportand implementsend_codemethodIn settings.py:OTP_PROVIDER={'TRANSPORT_TYPE':"SMS",# EMAIL/SMS'TRANSPORT_CLASS':'path.to.your.provider','CELERY':'path.to.your.celery.file'# Send code async}Then, in your code you may to use:generate_otp- to generate code and send itverify_otp- to verify payload from user
Package: django-otp-sms
django-otp-smsDjango приложение для аутентификации через SMSУстановкаДобавить “otp_sms” в ваш INSTALLED_APPS:INSTALLED_APPS = (
    ...
    'otp_sms',
)Выполнить миграцию:python manage.py migrateДобавить бекенд otp_sms.backends.SMSBackend в ваш AUTHENTICATION_BACKENDS:AUTHENTICATION_BACKENDS = (
    ...
    'otp_sms.backends.SMSBackend',
)Использовать представление otp_sms.views.SMSAuthenticationWizardView для аутентификации пользователей:from otp_sms.views import SMSAuthenticationWizardView

urlpatterns = patterns('',
    ...
    url(r'^login/', SMSAuthenticationWizardView.as_view(template_name='login.html'), name='login'),
    ...
)Указать в настройках адаптер для отправки SMS (на данный момент доступны: SMSRuAdapter и ProstorAdapter):OTP_SMS_ADAPTER = 'otp_sms.adapters.SMSRuAdapter'Указать учетные данные для выбранного адаптера:OTP_SMS_AUTH = {
    'KEY': <секретный ключ для sms.ru, например>
}НастройкиOTP_SMS_COUNT_ATTEMPTSколличество попыток для отправки SMSOTP_SMS_LATENCY_ATTEMPTSзадержка (timedelta) после использования всех попыток отправить SMS, после истечения задержки снова доступна отправка SMSOTP_SMS_AUTHучетные данные для выбранного адаптераOTP_SMS_TOKEN_TEMPLATEшаблон SMS, к примеру “Ваш пароль {token}”OTP_SMS_NOTIFY_ADMINS_ADAPTER_ERRORTrue или False, отправлять или нет администраторам ошибки при отправке смсOTP_SMS_TEST_MODEИспользуется для тестирования, если True любое значение является валидным токеном
Package: django-otp-twilio
This is a django-otp plugin that delivers tokens via Twilio’sSMSservice.Seedjango-otpfor more information
on the OTP framework.DevelopmentThis project is built and managed withhatch. If you don’t have hatch, I
recommend installing it withpipx:pipx install hatch.pyproject.tomldefines several useful scripts for development and testing.
The default environment includes all dev and test dependencies for quickly
running tests. Thetestenvironment defines the test matrix for running the
full validation suite. Everything is executed in the context of the Django
project in test/test_project.As a quick primer, hatch scripts can be run withhatch run[<env>:]<script>.
To run linters and tests in the default environment, just runhatch run check. This should run tests with your default Python version and
the latest Django. Other scripts include:manage: Run a management command via the test project. This can be used to
generate migrations.lint: Run all linters.fix: Run all fixers to address linting issues. This may not fix every
issue reported by lint.test: Run all tests.check: Run linters and tests.warn: Run tests with all warnings enabled. This is especially useful for
seeing deprecation warnings in new versions of Django.cov: Run tests and print a code coverage report.To run the full test matrix, runhatch run test:run. You will need multiple
specific Python versions installed for this.You can clean up the hatch environments withhatch env prune, for example to
force dependency updates.
Package: django-otp-u2f
Django OTP U2FDjango OTP plugin for U2F.Free software: GNU General Public License v3Documentation:https://django-otp-u2f.readthedocs.io.Installpip install django-otp-u2fINSTALLED_APPS = [
    ...
    'otp_u2f',
    ...
]History0.3.1 (2022-08-12)Fix key registration with fido2-1.0.0.0.3.0 (2022-07-19)Upgrade to fido2-1.0.0.Update supported Django versions.0.2.5 (2022-06-09)Depend on fido2<1 because >=1 has breaking changes.0.2.4 (2022-01-13)Allow form submission with keyboard.0.2.3 (2021-12-24)Delay key registration until the button is pressed to allow the user
to change the name of the key during registration.0.2.2 (2021-12-24)Restore compatibility with python 3.6.0.2.1 (2021-12-23)Fix missing import.0.2.0 (2021-12-23)Switch to the Web Authentication API.0.1.6 (2021-07-09)Fix device verification to return the device used to sign the
challenge instead of the device used to initiate the challenge.Switch to setuptools_scm for automatic git versioning.Move package data to setup.cfg.Switch django TestCase to pytest fixtures.Add Python 3.9 and Django 3.2 to the support matrix.Move test dependencies to the otp_u2f[test] extra.Switch to PEP517 package builder.Exclude tests from package.0.1.5 (2020-10-23)Update to replace botched release :-)0.1.4 (2020-10-23)Fix deprecation warnings in preparation of Django 4.Fix javascript logging call.0.1.3 (2019-11-07)Update minimum dependencies.Add test for current authentication method.0.1.2 (2019-11-07)Use package setup whilelist.Add original author.Remove python 2 classifiers.0.1.1 (2019-11-05)First release on PyPI.