semvec/pypi-packages huggingface dataset:
Flask-Logging 0.1.3
UNKNOWN
License: MIT

Flask-Logging
-------------

Filter certain requests from the Flask log. Useful during development
when requests fill up with /static/ URLs. Not for use in production,
Flask-Logging monkey patches the ``werkzeug`` logging function.

Installation
^^^^^^^^^^^^

::

    pip install flask-logging

Usage
^^^^^

::

    from flask.ext.logging import Filter
    filter = Filter('static')

Filters any request with the word 'static' from the log.

Filtering more than one word:

::

    filter = Filter('static', 'admin')

Updating the filter:

::

    filter = Filter('static')
    filter.filters = 'static', 'admin'
Jterator 0.0.1
A minimalistic pipeline engine
License: MIT

Jterator
========

A minimalistic pipeline engine with motivation to be flexible, but uncomplicated enough, so that no GUI is required to work with it.

* use simple format like JSON for basic parametrization whenever possible
** don't be afraid to keep your input settings on the disk
* for performance heavy IO use HDF5 
* used scientific data analysis.
* UNIX pipeline is a one great idea, but it is mostly restricted to text processing

Modules
-------


Think of your pipeline as a sequence of connected modules (a linked list). Each module is a program that get and reads JSON from on STDIN file descriptor.
Such JSON contains all the input settings required by the module.

Getting started 
---------------

Each pipeline has the following layout on the disk:

* **handles** folder contains all the JSON handles files, the are passed as STDIN to *modules*.
* **modules** folder contains all the executable plus code for programs corresponding
* **logs** folder contains all the output from STDOU and STERR streams, obtain for each executable that has been executed.
* **data** folder contains all the heavy data output like HDF5, etc. These data are shared between modules. 

Jterator allows only very simplistic type of workflow -  *pipeline* (somewhat similar to a UNIX-world pipeline). Description of such workflow must be put sibling to the folder structure described about, i.e. inside the Jterator pipeline (project) folder. Recognizable file name must be one of **['JteratorPipe.json', 'jt.pipe']**. Description is a JSON format. 

```json
{	
	"name": "Foo",
	"version": "0.0.1",	
	"pipeline": [
		{
			"name": "Bar",
			"module": "bar",
			"handles": "handles/some_bar"
		}, {
			"name": "Baz",
			"module": "baz",
			"handles": "handles/some_baz"
		}
	],
	"tests": [
		{
			"type": "hdf5_dependency",
			"module_name": "baz",
			"input": ["bar"],
			"output": ["baz"]
		}
	]
}

```

To *run* your first pipeline, do:

```bash
cd /my/first/jterator/pipeline/folder && jt run
```



Developing new modules
======================

This is a small walk-through on how to develop a new module for *Jterator*. Each module as to follow a particular convention of processing input  parameters. It can be written in virtually any programming language as long as such language can provide tools for working with *JSON* and *HDF5* data formats.

Developing Jterator
===================

Latest code is available at https://github.com/ewiger/Jterator

Nose tests
----------

We use nose framework to achieve code coverage with unit tests. In order to run tests, do

```bash
cd tests && nosetests
```
ConwayCPU 0.5
The Game of Life, living on your CPU
License: MIT
Keywords: terminal,tty,console,game,life

Metadata-Version: 1.0
Name: ConwayCPU
Version: 0.0
Summary: The Game of Life, living on your CPU
Homepage: http://pypi.python.org/pypi/ConwayCPU/
Author: Rupert Deese
Author-email: hartdeese@mac.com
License: MIT
Description: ======
        ConwayCPU
        ======
        
        ConwayCPU is an implementation of Conway's game of Life that
        lives in a console window. The rules of the game have been changed
        slightly to allow for the influence of your computer's CPU usage.
        ConwayCPU's life is more virile (look for the yellow cells!)
        when your CPU is busy--and returns to its normal self when your 
        computer is idle.

        This project is a half-baked idea of mine that I hope you enjoy, but
        I want to credit Eric Rose and Giampaolo Rodola for their packages,
        which made this much easier to create.
        
        .. _psutil library: https://pypi.python.org/pypi/psutil
        .. _original conway package: https://pypi.python.org/pypi/conway/1.1
        .. _Blessings terminal library: http://pypi.python.org/pypi/blessings/
        
        
        Features
        ========
        
        * Runs a fullscreen Game of Life world in your console.
        * Makes Life more interesting by "loosening the rules" probabilistically
        according to how active the CPU is. Yellow colored cells in the game are
        the ones created by CPU activity.
        * The life environment is split into as many vertical sections as your
        machine has cores, with each core's activity only affecting the Life in
        its section.
        
        
        Getting it running
        ==================
        
        ::
        
            pip install conwayCPU
            conwayCPU.py
        
        Sit back and enjoy Life.

            If your computer is really powerful and you don't often come near
            max CPU usage, you can pass the script an argument between 0 and 1
            for the program to treat as "max cpu usage".
        
        Kudos
        =====
        
        A very simple extension of the pip package 'conway'. Credit to Eric Rose
        for the original package.
        
        
        Version History
        ===============
        
        0.0 Initial Release