semvec/pypi-packages huggingface dataset:
django-api-docs 1.1.1
Interactive API Documentation
License: MIT
Keywords: django-interactive-api-docs

#Overview

This application is based upon interactive API Docs from the Mashery.  Interactive docs allow your API consumers to see exactly
how your APIs are called and what results they should expect.  Take a look at api.stegelman.com for an example of how
this app is implemented.


## Read Some Docs

http://readthedocs.org/docs/django-api-docs/en/latest/


## Pip

pip install django-api-docs
dpm 0.10
dpm (data package): data packaging system and utilities
License: MIT
Keywords: data,packaging,component,tool

Introduction
============

dpm (data package manager) is a command line tool and python library for
working with `Data Packages`_ and interacting with data repositories like
`the Data Hub`_.

For more information visit the documentation at:
http://readthedocs.org/docs/dpm/

.. _`Data Packages`: http://wiki.ckan.org/Data_Package
.. _`the Data Hub`: http://thedatahub.org/

Installation
============

See doc/install.rst or the online documentation.


License
=======

See doc/license.rst


For Developers
==============

1. Building the documentation.

You need sphinx (python-sphinx) to do this. Now you can build the docs::

    python setup.py build_sphinx

2. Running tests. We suggest you use nose::

    nosetests dpm/tests/
  
  To exclude tests depend on access to the internet::

    nosetests -a \!__external__ dpm/tests
verobject 0.1.4
Version controlled object database on Redis
License: MIT

.. -*-rst-*-

===========
 verobject
===========

:name:        verobject
:description: Version controlled object database on Redis
:copyright:   © 2012 Justine Alexandra Roberts Tunney
:license:     MIT


What Is This?
=============

It's a key value store that keeps copies of past revisions.

Why you should use this
-----------------------

- You've already deployed Redis
- You don't ever want to lose data
- You like pythonic APIs
- You want the KVS to automatically pickle (or jsonify) your data
- You want something simple (140 source lines of code)
- You want something that works (70 lines of test code)

Why you shouldn't use this
--------------------------

- It's space inefficient.  It doesn't compress revision deltas like git does.
- It doesn't support transactions or fancy save methods like zope


Installation
============

From folder::

    sudo python setup.py install

From cheeseshop::

    sudo pip install verobject

From git::

    sudo pip install git+git://github.com/jart/verobject.git


Basic Usage
===========

::

    import datetime, verobject, redis
    redis = redis.Redis()
    table1 = verobject.Store('table1', redis=redis)

    table1['hk'] = {'hello': ['kitty', 'kitty', 'kitty']}
    table1['ts'] = datetime.date(1984, 10, 31)
    print table1['ts'], table1['hk']
    del table1['ts']

    table1['vc'] = 'version1'
    table1['vc'] = 'version2'
    table1['vc'] = 'version3'
    assert list(table1.versions('vc')) == ['version3', 'version2', 'version1']
    assert table1.versions('vc')[0] == 'version3'
    assert table1.versions('vc')[-1] == 'version1'
pyrsync 0.1.0
A Python module which implements rsync with SHA256 hash.
License: MIT

===============================
#pyrsync
===============================
pyrsync is a Python module which implements the [rsync algorithm] [1], 
written in pure Python. It *is not* a wrapper for rsync, but a set of 
functions which apply full rsync functionality through Python.

The original rsync specification calls for the use of an MD5 hash, which
the developers of this module considers to be outdated, and thus all 
occurences of MD5 have been replaced with SHA256. Personally, I would
opt for using SHA512, but this would double the storage size for hash
table databases. SHA256 is sufficient to meet standard security 
requirements for verification processes as of this release, although,
eventually, added functionality for the user/developer to choose between
various hashes should be considered for further releases.

The majority of the code for this module is taken from [Eric Pruitt's
post at ActiveState] [1]. It was orginally licensed under an [MIT license]
[2], and this license has been kept wthout modifications.

## Installation
--------------------------------
If you have [setuptools] [3] installed, simply do:

    $ sudo python setup.py install

If you do not have setuptools, the setup.py script will detect this and 
default to using the python builtin distutils. To install using distutils,
the installation process is the same as documented above for setuptools.

## Use
--------------------------------
An example use case for this module:

    # On the system containing the file that needs to be patched
    >>> import pyrsync
    >>> unpatched = open("unpatched.file", "rb")
    >>> hashes = pyrsync.blockchecksums(unpatched)

    # On the remote system after having received hashes
    >>> import pyrsync
    >>> patchedfile = open("patched.file", "rb")
    >>> delta = pyrsync.rsyncdelta(patchedfile, hashes)

    # System with the unpatched file after receiving delta
    >>> unpatched.seek(0)
    >>> save_to = open("locally-patched.file", "wb")
    >>> pyrsync.patchstream(unpatched, save_to, delta)

[1]: http://samba.anu.edu.au/rsync/ "Andrew Tridgell and Paul Mackerras. The rsync algorithm. Technical Report TR-CS-96-05, Canberra 0200 ACT, Australia, 1996."
[2]: https://code.activestate.com/recipes/577518-rsync-algorithm/ "Rsync Algorithm (Python Recipe)"
[3]: http://www.opensource.org/licenses/mit-license.php "OSI MIT License"