semvec/pypi-packages huggingface dataset:
spectrometers 0.0.3
API for spectrophotometers (pre-alpha)
License: BSD

spectrometers
~~~~~~~~~~~~~~~

Spectrometers is a simple python API for working with
spectrometers/spectrophotometers. This was originally created as a gist to help
with development of `openSpectrometer`_. This doesn't do anything interesting
yet.

.. _`openSpectrometer`: http://openspectrometer.com/

Example usage
----------

here you go

.. code-block:: python

    from spectrometers.devices import Nanodrop

    nanodrop = Nanodrop()

    wavelengths = nanodrop.capture()

    >>> wavelengths
    [0.500, 0.520]

Install
----------

.. code-block:: bash

    sudo pip install spectrometers

or maybe you hate package managers,

.. code-block:: bash

    sudo python setup.py install

Testing
----------

.. code-block:: bash

    make test

Changelog
----------

* 0.0.3: get unit tests passing

* 0.0.2: really minor README tweaks

* 0.0.1: basic python module

License
----------

BSD
wallaby-backend-elasticsearch 0.1.31
Asynchronous elasticsearch backend - part of Wallaby. The couchDB application framework.
License: BSD

wallaby-backend-elasticsearch
=============================

This package provides an asynchronous python interface to elasticsearch (using twisted).

For more information on wallaby visit http://wlby.freshx.de

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

You can install the elasticsearch backend with pip

```bash
pip install wallaby-backend-elasticsearch
```

How to use
==========

The library is based on twisted's asynchronous pattern. To use the library in an asynchronous fassion you 
first need to create an reactor based application:
 
```python
from twisted.internet import defer

@defer.inlineCallbacks
def run():
    # wait 1 second
    d = defer.Deferred()
    reactor.callLater(1.0, d.callback)
    yield d

    # stop the reactor and quit the application
    reactor.stop()

from twisted.internet import reactor
reactor.callWhenRunning(run)
reactor.run()
```

Now we can connect to an existing elasticsearch cluster:

```python
@defer.inlineCallbacks
def run():
    # Create elasticsearch client object
    from wallaby.backends.elasticsearch import Connection
    es = Connection(
        baseURL="http://localhost:9200",
        index="<name of index>",
        username="<username>", 
        password="<password>",
    )

    # Send query
    res = yield es.doQuery({
            "query": {
                "query_string": {
                    "query": "*"
                }
            }
        })

    # stop the reactor and quit the application
    reactor.stop()
```
user-messages 0.1.1
a reusable private user messages application for Django
License: BSD

User messaging
==============

``user-messages`` is an application for allowing users of your Django site to
send messages to each other.


Quick Start
-----------

Include ``user-messages`` in your requirements file and add
``"user_messages"`` to your INSTALLED APPS setting.

Once you have the ``user-messages`` installed, hook up the URLs::
    
    urlpatterns = patterns("",
        # some cool URLs
        
        (r"^messages/", include("user_messages.urls")),
        
        # some other cool URLs
    )

Now all you need to do is wire up some templates.
SyncHg 1.0.0
A simple script & library to handle syncing remote mercuial repositories
License: BSD

Ever had to keep two mercurial repositories on different machines in sync?
Mercurials push & pull help to make this fairly easy, but if you make use of
mercurial queues or the histedit extension then it can quickly become tedious.
That's where synchg comes in.  

Synchg intends to make syncing two mercurial repositories as simple as
possible.  Simply run a command, and synchg will take care of the rest.

Requirements
============

Python 2.7 & Mercurial 2.3 are recommended, though others will probably work.

Synchg depends on these python packages:

* `Plumbum <https://github.com/tomerfiliba/plumbum>`_
* `Clint <https://github.com/kennethreitz/clint>`_

It also requires:

* An ssh client on the path (putty on windows, openssh compatible on other
  platforms)
* Access to an SSH server on the remote machine(s)
* An ssh private key loaded in an ssh agent (pagaent on windows, ssh-agent on
  other platforms)
* That the `mq <http://mercurial.selenic.com/wiki/MqExtension>`_ extension is
  enabled on the remote machine(s)

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

Synchg and it's python dependencies can be installed via pip::
  
  $ pip install synchg

Using SyncHg
=============

The synchg script should be run from the command line::

  $ synchg remote_host [local_path=None]

Where ``remote_host`` is the host you wish to sync with and ``local_path`` is
the optional path to the local mercurial repository (if missing, the current
directory will be assumed)

Information on more options can be found by running::

  $ synchg --help

.. CAUTION::

    Synchg regards remote repositories as "slaves" and will strip out any
    changesets it finds that are not in the local repository.  You will be
    prompted before this happens, but the script will be unable to continue if
    you don't answer yes.

Configuration 
---------------

On first run of synchg you will be prompted with some configuration options:

Remote source directory
    This is the path on the remote under which all your repositories should be
    found.
    For example, if you have repositories at ``/repo/one/`` and ``/repo/two/``
    then you would set this to ``/repo/``

If you want to change the configuration of synchg, then simply run ``synchg
-c`` to run the config process again.