semvec/pypi-packages huggingface dataset:
mpcouch 0.2.7
A multiprocess bulk-uploading helper for CouchDB
License: MIT
Keywords: couchdb multiprocessing upload bulk

Multiprocess Bulk Uploading to CouchDB
######################################

Status
======

This is not yet finished, but can already be used.

History
=======


v 0.2.7
-------

* Updated readme

v 0.2.6
-------

* Introduced the ``jobsbuffersizemax`` argument to limit the amount of upload-processed buffered in working memory. Now it is possible to work on data of infinite size.

v 0.2.5
-------

* only spawn one concurrent process for performing uploads

v 0.2.4
-------

* working version, still spans unlimited amount of processes


Usage
=====

Create a new mpcouchPusher object

.. code-block::
    
    myCouchPusher = mpcouch.mpcouchPusher( "http://localhost:5984/myDatabase", 30000 )

If the data is created faster than the upload happens, it might be necessary to let the generation of new documents pause befor allowing another batch-upload process to be buffered. The amount of bufferd upload-processes is specified by the optional ``jobsbuffersizemax`` argument which defaults to 10. This means that when there are 10 batch-upload processes already waiting in line to be executed, the module holds the main python thread until one process has finished.
By adjusing this value it is possible to find an equilibrium between upload-buffer (working memory) and document generation speed.

Use this object every time you have one single document ready to be stored in the database:

.. code-block::
    
    myCouchPusher.pushData(myNewDocument)

The module will collect all documents until the threshold is reached (in our example this would be the 30000 specified above) and upload them as a batch to the CouchDB also specified at creation time of the object (myCouchDbDatabase).

Since every bulk-upload is performed by a single process, the original program continues while the upload happens in the background.

To wait for all running uploads to finish and to make sure the very last batch of documents gets pushed to the server, run

.. code-block::
    
    myCouchPusher.finish()

after your final document was sent to pushData.
The module now waits for all the uploads to finish and uploads the final bulk of collected documents.
etest 1.0.0
Ebuild Testing Framework
License: MIT
Keywords: ebuild,test,gentoo,portage,emerge

Description
===========

Framework for testing ebuilds.

Using Docker to provide consistent sandboxed environments, etest runs ebuilds
through several tests (implicitly and explicitly defined).  Every ebuild gets
many containers created to run every testing scenario in isolation.  Testing
scenarios are created from combinations of USE flags, features (test or no
test), as well as custom commands provided in the hints files.

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

This package is available in my overlay, alunduil, and can be installed on
Gentoo quite easily::

    layman -a alunduil
    emerge app-portage/etest

This package is also stored in PyPI and can be installed the standard way::

    pip install etest

The latest release available is:

.. image:: https://badge.fury.io/py/etest.png
    :target: http://badge.fury.io/py/etest


 ``etest`` does require a running docker daemon but does not explicitly list it
 as a requirement.  It's not explicitly listed since the docker daemon doesn't
 necessarily need to be local.  Non-local docker daemons are not currently
 supported.

Using etest
===========

.. note::
    etest requires a running docker daemon (either local or remote).  If using
    a remote docker instance you must set the DOCKER_HOST environment variable
    with the hostname (just like compose).

To get started simply run ``etest`` in a directory that contains ebuilds in a
valid overlay.

Alternatively, while still in a valid overlay directory or subdirectory, a list
of ebuilds can be passed to ``etest`` to run tests only against those ebuilds::

    # Run all etest tests for all ebuild versions.
    cd /var/lib/layman/alunduil
    etest app-portage/etest

    # Run all etest tests for the specified ebuild.
    cd app-portage/etest
    etest etest-9999.ebuild

More advanced usage of this package is outlined in the built-in help::

    etest --help

Developing etest
================

If you would prefer to clone this package directly from git or assist with 
development, the URL is https://github.com/alunduil/etest.

etest is tested continuously by Travis-CI and running the tests is quite 
simple::

    flake8
    python setup.py test

System tests can be run as well but require a working docker daemon as well as
approximately two and half hours::

    nosetests test_etest/test_system

The current status of the build is:

.. image:: https://secure.travis-ci.org/alunduil/etest.png?branch=master
   :target: http://travis-ci.org/alunduil/etest

Known Issues
============

Known issues can be found in the github issue list at
https://github.com/alunduil/etest/issues.

Troubleshooting
===============

If you need to troubleshoot an issue or submit information in a bug report, we
recommend obtaining the following pieces of information:

* output with verbose output turned on
* any relevant stack traces