semvec/pypi-packages huggingface dataset:
python-opengraph 0.0.2
Python module to parse Open Graph metadata on web pages
License: MIT

.. image:: https://travis-ci.org/HenrikOssipoff/python-opengraph.svg?branch=master
    :target: https://travis-ci.org/HenrikOssipoff/python-opengraph
.. image:: https://coveralls.io/repos/HenrikOssipoff/python-opengraph/badge.svg?branch=master :target: https://coveralls.io/r/HenrikOssipoff/python-opengraph?branch=master

Python module to parse Open Graph metadata on web pages. For more information on the Open Graph Protocol, see http://ogp.me/.

**This repository is currently work in progress, and APIs may change without notice.**

Installation
============
.. code:: python

    pip install python-opengraph
Active-SQLAlchemy 0.4.0
==================
Active-SQLAlchemy
==================

A framework agnostic wrapper for SQLAlchemy that makes it really easy
to use by implementing a simple active record like api, while it still uses the db.session underneath

:copyright: © 2014/2015 by `Mardix`.
:license: MIT, see LICENSE for more details.
License: MIT
Keywords: sqlalchemy,flask,active sqlalchemy,orm,active record,mysql,postgresql,pymysql,pg8000,sqlite

==================
Active-SQLAlchemy
==================

A framework agnostic wrapper for SQLAlchemy that makes it really easy
to use by implementing a simple active record like api, while it still uses the db.session underneath

:copyright: © 2014/2015 by `Mardix`.
:license: MIT, see LICENSE for more details.
bowerrecipe 0.2
zc.buildout recipe to install static resources using Twitter Bower.
License: MIT

.. contents::

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

This recipe allows downloading and installing assets such as images, CSS and JavaScript using Twitter Bower.

Supported options
=================

The recipe supports the following options:

packages
    Packages that should be installed with bower. Packages specified here are
    passed to bower verbatim. They can be specified in any form that is
    supported by bower::

        packages =
            underscore
            git://github.com/components/jquery.git
            bootstrap#2.2.2

base-directory
    Absolute path to the bower "project" directory. ``bower install`` is run
    from this directory and the bower configuration file, ``.bowerrc`` is also
    placed here.  Optional; defaults to ``${buildout:parts-directory}/bower``.
    Requires an absolute path.

    This directory is not removed when the Buildout part is uninstalled.

executable
    Absolute path to the ``bower`` executable. Packages are installed using
    this executable. Optional; defaults to ``bower`` on ``PATH``.

downloads
    Relative path, from the ``base-directory``, to the directory where bower
    will download packages to. This path is written to the ``.bowerrc`` file
    prior to running the executable. Optional; defaults to ``downloads``. Thus,
    the downloaded packages are placed in ``${base-directory}/downloads`` by
    default.

    This directory *is* removed when the Buildout part is uninstalled.


Example usage
=============

A sample buildout that uses this recipe could look like::

    [buildout]
    parts = node web

    [node]
    recipe = gp.recipe.node
    url = http://nodejs.org/dist/v0.8.16/node-v0.8.16.tar.gz
    npms = bower@0.6.8
    scripts = bower

    [web]
    recipe = bowerrecipe
    packages = jquery#1.8.3 normalize-css
    executable = ${buildout:bin-directory}/bower

This would place the downloaded packages in ``parts/bower/downloads``.
Modifying the ``web`` section to be::

    [web]
    recipe = bowerrecipe
    packages = jquery#1.8.3 normalize-css
    executable = ${buildout:bin-directory}/bower
    base-directory = ${buildout:parts-directory}
    downloads = components

would result in bower placing the downloaded packages in ``parts/components``.

Notes
=====

#. Bower still looks at the ``~/.bowerrc`` file. Hence, if this file exists, it
   may affect the buildout bower configuration
#. Bower still uses the cache located in the user's home directory. For me,
   this happens to be ``~/.bower/cache/``


Contributors
============

Anshuman Bhaduri
Sebastian Wehrmann


Changelog
=========

0.2
-----

- Fix removal of base directory upon uninstall. (#1)

- Update files on every buildout run, rather loading them once.

0.1.1
-----

- Fixed documentation so it displays correctly on PyPI
  [Anshuman Bhaduri]

0.1
---

- Created initial recipe
  [Anshuman Bhaduri]


Download
========
snakeMQ-PubSub 0.1.0
An implementation of the publish-subscribe pattern for snakeMQ.
License: MIT
Keywords: snakeMQ,pubsub

snakeMQ-PubSub
==============

|Build Status| |Coverage Status| |Docs|

An implementation of the publish-subscribe pattern for snakeMQ.

Includes a Publisher, Subscriber, and Broker.

Contributing
------------

Submit a pull request and make sure to include an updated AUTHORS
with your name along with an updated CHANGES.rst.


License
-------

MIT

.. |Build Status| image:: https://travis-ci.org/repole/snakemq-pubsub.svg?branch=master
   :target: https://travis-ci.org/repole/snakemq-pubsub
.. |Coverage Status| image:: https://coveralls.io/repos/repole/snakemq-pubsub/badge.svg?branch=master
   :target: https://coveralls.io/r/repole/snakemq-pubsub?branch=master
.. |Docs| image:: https://readthedocs.org/projects/snakemq-pubsub/badge/?version=latest
   :target: http://snakemq-pubsub.readthedocs.org/en/latest/
cacpy 0.5.2
A python wrapper for the cloudatcost.com API - https://github.com/cloudatcost/api
License: MIT
Keywords: wrapper for cloud at cost api

==================
python-cloudatcost
==================

``python-cloudatcost`` is a light-weight Python wrapper for the `Cloud at Cost REST API`_.

-----
usage
-----
::

    from cacpy import CACPy
    cac = CACPy('email@example.com','API_KEY')
    srv_info = cac.get_server_info()

More details and the latest updates can be found on the `GitHub Project Page`_.

.. _Cloud at Cost REST API: https://github.com/cloudatcost/api
.. _GitHub Project Page: https://github.com/adc4392/python-cloudatcost