semvec/pypi-packages huggingface dataset:
tornado-razorpay 0.1.3
Razorpay Asynchronous Tornado Python Client
License: MIT
Keywords: razorpay payment gateway india tornado async

Razorpay Python Client
======================

Python ASYNC bindings for interacting with the Razorpay API.

Installation
------------

1. Through pip: ``pip install tornado-razorpay``

2. Manually: ``python setup.py install``

Usage
-----

You need to setup your key and secret using the following: You can find
your API keys at https://dashboard.razorpay.com/#/app/keys.

.. code:: py

    from tornado_razorpay import Client
    razor = Client("<YOUR_API_KEY>", "<YOUR_API_SECRET>")

Payments
~~~~~~~~

-  Capture a payment

   .. code:: py

       await razor.payment.capture("<PAYMENT_ID>", "<AMOUNT>")

-  Fetch a particular payment

   .. code:: py

       await razor.payment.fetch("<PAYMENT_ID>")

-  Fetch all payments

   .. code:: py

       await razor.payment.all()

Refunds
~~~~~~~

-  Initiate a refund

   .. code:: py

       await razor.refund.create("<PAYMENT_ID>")  # for whole amount
       await razor.refund.create("<PAYMENT_ID>", data={"amount": "<AMOUNT_TO_BE_REFUNDED>"})  # for particular amount

-  Fetch a particular refund

   .. code:: py

       await razor.refund.fetch("<PAYMENT_ID>", "<REFUND_ID>")

-  Fetch all refunds for a particular payment

   .. code:: py

       await razor.refund.all("<PAYMENT_ID>")

Compliance and Errors
~~~~~~~~~~~~~~~~~~~~~

-  Response that you receive from the functions is
   ```tornado.httpclient.HTTPResponse``
   object <http://tornadokevinlee.readthedocs.io/en/latest/httpclient.html#response-objects>`__
   For the success of your API call can be determined if
   ``response.code == 200`` is ``True``. Please handle Errors
   accordingly.

NOTE: You will have to use Tornado's IOLoop to use this API in Async. If
you are looking for Sync API's or don't know what this is, please go to
https://github.com/razorpay/razorpay-python.
opentest 0.9
open test Project
License: MIT
Keywords: sample setuptools development

A sample Python project
=======================

A sample project that exists as an aid to the `Python Packaging User Guide
<https://packaging.python.org>`_'s `Tutorial on Packaging and Distributing
Projects <https://packaging.python.org/en/latest/distributing.html>`_.

This projects does not aim to cover best practices for Python project
development as a whole. For example, it does not provide guidance or tool
recommendations for version control, documentation, or testing.

----

This is the README file for the project.

The file should use UTF-8 encoding and be written using ReStructured Text. It
will be used to generate the project webpage on PyPI and will be displayed as
the project homepage on common code-hosting services, and should be written for
that purpose.

Typical contents for this file would include an overview of the project, basic
usage examples, etc. Generally, including the project changelog in here is not
a good idea, although a simple "What's New" section for the most recent version
may be appropriate.
cmsplugin-porticus 0.5.0
Porticus plugins for DjangoCMS
License: MIT

.. _DjangoCMS: https://www.django-cms.org
.. _South: http://south.readthedocs.org/en/latest/
.. _Porticus: https://github.com/emencia/porticus

cmsplugin_porticus
==================

This is the `DjangoCMS`_ plugins for `Porticus`_ to embed *Album* or *Galleries* in a cms page.

Links
*****

* Download his `PyPi package <http://pypi.python.org/pypi/cmsplugin-porticus>`_;
* Clone it on his `Github repository <https://github.com/emencia/cmsplugin-porticus>`_;

Requires
********

* Django >= 1.7;
* `DjangoCMS`_ >= 3.1;
* `Porticus`_ >= 1.0.0 (for *Porticus < 0.9* and so for *DjangoCMS 2.x* use the plugin version *<0.2* from the branch *djangocms_2*);

**Warning:** Since ``0.3.0``, database migration has been switched to Django 1.7 migrations system and `South`_ support has been dropped. The `South`_ migration files are still there but moved to ``south_migrations``, resulting in you need ``south==1.x`` to use them. This is only needed if you need to migrate project datas to the last Porticus version, you don't have to care about this if you just start a new project.

Last release version compatible with Django <= 1.6 + `DjangoCMS`_ 3.0 and `Porticus`_ 0.9 is still available on branch ``django_1-6``.

Optional
---------

* `South`_ migration is supported;

Install
*******

In your ``INSTALLED_APPS`` setting : ::

    INSTALLED_APPS = (
        ...
        'cmsplugin_porticus',
        ...
    )

Then add its settings : ::

    from cmsplugin_porticus.settings import *

See the plugin ``settings.py`` file to see what settings you can override.

Usage
*****

Once installed you can insert porticus Galleries or Albums in your page through the CMS toolbar. Each Porticus content in your pages can use a template from the defined ones in your settings.

For Album cloud tags if enabled, you will need to do some CSS to manage size diff between tags, class name start from tag-size-1 to tag-size-XXX where XXX is equivalent to ``settings.PORTICUS_ALBUM_PLUGIN_CLOUD_STEPS`` value (default is 6). Cloud tag html lives inside ``porticus/cms/album_detail.html``.