semvec/pypi-packages huggingface dataset:
laterpay-client 5.9.0
LaterPay API client
License: MIT
Keywords: LaterPay API client

laterpay-client-python
======================

.. image:: https://img.shields.io/pypi/v/laterpay-client.png
    :target: https://pypi.python.org/pypi/laterpay-client

.. image:: https://img.shields.io/travis/laterpay/laterpay-client-python/develop.png
    :target: https://travis-ci.org/laterpay/laterpay-client-python

.. image:: https://img.shields.io/coveralls/laterpay/laterpay-client-python/develop.png
    :target: https://coveralls.io/r/laterpay/laterpay-client-python


`LaterPay <http://www.laterpay.net/>`__ Python client.

If you're using `Django <https://www.djangoproject.com/>`__ then you probably want to look at `django-laterpay <https://github.com/laterpay/django-laterpay>`__

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

::

    $ pip install laterpay-client

Usage
-----

See http://docs.laterpay.net/

Development
-----------

See https://github.com/laterpay/laterpay-client-python

`Tested by Travis <https://travis-ci.org/laterpay/laterpay-client-python>`__

Release Checklist
-----------------

* Install ``twine`` with ``$ pipsi install twine``
* Determine next version number from the ``CHANGELOG.md`` (ensuring we follow `SemVer <http://semver.org/>`_)
* ``git flow release start $newver``
* Ensure ``CHANGELOG.md`` is representative
* Update the ``CHANGELOG.md`` with the new version
* Update the version in ``setup.py``
* Update `trove classifiers <https://pypi.python.org/pypi?%3Aaction=list_classifiers>`_ in ``setup.py``
* ``git flow release finish $newver``
* ``git push --tags origin develop master``
* ``python setup.py sdist bdist_wheel``
* ``twine upload dist/laterpay*$newver*`` or optionally, for signed releases ``twine upload -s ...``
* Bump version in ``setup.py`` to next likely version as ``Alpha 1`` (e.g. ``5.1.0a1``)
* Alter trove classifiers in ``setup.py``
* Add likely new version to ``CHANGELOG.md``
jta.qsutil 0.1.1
A library for parsing URL query strings into heterogeneously shaped dicts.
License: MIT
Keywords: query string,querystring,URL,parser

The specifications that define the makeup of URLs are
very flexible when it comes to what makes up the query string portion (the part
after the `?`). Many web services have taken the initial recommendation of using
`key=value` pairs to another level by allowing complex structures to be
represented for a sacrifice in parsing performance.

The goals of this project are:
* Be able to process sequence and sub-mapping hints in URL query string keys.
* Only shape values into sequences if there are multiple occurrences of the same
 key or the key contains a sequence hint.
* Remain standards-compliant with URI and URL RFC specs.
* Provide an API similar to Python 3's standard urllib.
* Be Python 2 and 3 compatible without relying on a compatibility library.