semvec/pypi-packages huggingface dataset:
oly 1.0.33
Oly Cli
License: MIT
Keywords: cli development console docker

Oly - CLI
==========

Oly is a command line tool that allows developers to manage services. 

Supported Platforms
-------------------

Oly has been tested and is known to run on Linux (Ubuntu), Mac OS X
(10.4, 10.5, 10.6), and Solaris (10 for Intel) and FreeBSD 6.1.  It will
likely work fine on most UNIX systems.

Windows not tested yet...

Oly is intended to work on Python 3 version 3.* or later
and on Python 2 version >2.7.

Documentation
-------------

--

Reporting Bugs, and Viewing the Source Repository
---------------------------------------------------------------

Please report bugs in the [Github issue tracker](https://github.com/glikaj/oly/issues)

You can view the source repository for oly via [https://github.com/glikaj/oly](https://github.com/glikaj/oly)


Contributing
------------

If you'd like to contribute to oly directly, please contact me directly
ernest 0.1.6
A CLI-based tool for making bulk changes to file text.
License: MIT

# Ernest

## What Ernest is
1. A CLI-based tool for making bulk changes to files via Python, partly achieved through syntax trees (for .py files, using [redbaron](https://github.com/PyCQA/redbaron)) and partly through regular expressions.
2. Useful if you're making a load of really boring changes that you can't really do with regexes alone (or only with regexes the length of War and Peace).
2. Named after the [Nitpicker](http://theadventurezone.wikia.com/wiki/Nitpicker) from The Adventure Zone.

It was made as part of a refactoring effort for a specific project and as such is pretty limited at the moment - it currently only contains methods for refactoring Python files but it is intended to be extensible.

## What Ernest isn't
1. A tool that will fix all your syntax problems. 
2. Pulling from any set of code standards - any new refactorings have to defined _manually_ (though you can pick and choose which ones to apply).
3. Particularly reliable.

## Installation

```sh
pip install ernest
```

## Configuration
You can override the defaults by making a JSON config file. By default Ernest looks in `~/.config/ernest/ernest.json` but you can specify a different json file using the `--config` option.

```json
{
  "name": "",  // the name of the project - used in headers
  "header": [  // added at the top of python files
    "#!/usr/bin/env python",
    "# encoding: utf-8",
    "This file is part of the {} project",  // example of how the name is used
    ""
  ],
  "imports": {  // checks python imports
    "exclude": [],  // do not allow these ever
    "conditional_exclude": {},  // do not allow these submodules from the main module, e.g. {'ernest': 'models'} excludes 'ernest.models' but allows 'ernest.helpers'
    "conditional_include": {}  // allow only these submodules from the main module, e.g. {'ernest': 'models'} allows 'ernest.models' but not 'ernest.helpers'
  }
}
```

You can find an example of the config file in the [data](data/ernest.json) folder.

## Usage
### Quickstart
```bash
ernest /project/path fix py
```

### General Options
```sh
--config /path/to/config
--name "My Project"
```

### Subcommands
#### `stats`
```bash
ernest [--config /path/to/config] [--name "My Project"] [/path/to/dir] stats [filetypes]
```

Show statistics for all files:
```bash
ernest /path/to/dir stats
```

Stats for just (e.g.) `txt` and `md` files:
```bash
ernest /path/to/dir stats txt md
```

#### `fix`
```bash
ernest [--config /path/to/config] [--name "My Project"] [/path/to/dir] fix [filetype] [fix(es)]
```

Run all fixes for `.py` files:
```bash
ernest /path/to/dir fix py all
```

Run the _literal string quote_ and _docstring quote_ fixes for `.py` files:
```bash
ernest /path/to/dir fix py literal docstring
```

## Contributing
Please feel free to fork, submit pull requests, etc.! It doesn't have to be limited to Python files - that's just how Ernest processes the text.
trackball 0.0.1
Python library for the Pimoroni Trackball breakout
License: MIT
Keywords: Raspberry Pi

Pimoroni Trackball Breakout
===========================

|Build Status| |Coverage Status| |PyPi Package| |Python Versions|

Installing
==========

Stable library from PyPi:

-  Just run ``sudo pip install trackball``

Latest/development library from GitHub:

-  ``git clone https://github.com/pimoroni/trackball-python``
-  ``cd trackball-python``
-  ``sudo ./install.sh``

.. |Build Status| image:: https://travis-ci.com/pimoroni/trackball-python.svg?branch=master
   :target: https://travis-ci.com/pimoroni/trackball-python
.. |Coverage Status| image:: https://coveralls.io/repos/github/pimoroni/trackball-python/badge.svg?branch=master
   :target: https://coveralls.io/github/pimoroni/trackball-python?branch=master
.. |PyPi Package| image:: https://img.shields.io/pypi/v/trackball.svg
   :target: https://pypi.python.org/pypi/trackball
.. |Python Versions| image:: https://img.shields.io/pypi/pyversions/trackball.svg
   :target: https://pypi.python.org/pypi/trackball

0.0.1
-----

* Initial Release
loggingex 1.2.0
Logging Extensions
License: MIT
Requires Python: >=3.5

##################
Logging Extensions
##################

.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
    :target: https://github.com/ambv/black

.. image:: https://img.shields.io/github/license/open-things/loggingex.svg
    :target: https://github.com/open-things/loggingex/blob/master/LICENSE

.. image:: https://travis-ci.com/open-things/loggingex.svg?branch=master
    :target: https://travis-ci.com/open-things/loggingex

.. image:: https://img.shields.io/pypi/v/loggingex.svg?color=green
    :target: https://pypi.org/project/loggingex/

.. image:: https://img.shields.io/pypi/pyversions/loggingex.svg
    :target: https://pypi.org/project/loggingex/

.. image:: https://img.shields.io/pypi/dm/loggingex.svg
    :target: https://pypi.org/project/loggingex/

Implements a few extensions for the standard python logging library.

Currently, this project lacks documentation. Sorry about that.


Logging Context Filter
======================

Logging Context Filter injects context variables into LogRecord objects as extra
fields.

Here's a usage example:

.. code-block:: python

    import logging
    import sys

    from loggingex.context import LoggingContextFilter, context

    log = logging.getLogger()


    def process_lines(lines):
        for index, line in enumerate(lines):
            line = line.strip()
            with context(current_line=index + 1):
                log.debug("processing line: %s", line)
                if not line:
                    log.error("empty line!")
                    continue
                log.info("processed line: %s", line)


    def process_files(filenames):
        log.debug("starting...")
        for filename in filenames:
            with context(current_file=filename):
                log.info("processing file: %s", filename)
                with open(filename, "r") as f:
                    process_lines(f)
                log.info("processed file: %s", filename)
        log.debug("work is complete!")


    if __name__ == "__main__":
        formatter = logging.Formatter(
            "%(current_file)s:%(current_line)s:%(levelname)s: %(message)s"
        )
        handler = logging.StreamHandler(stream=sys.stdout)
        handler.setFormatter(formatter)
        handler.setLevel(logging.DEBUG)
        handler.addFilter(LoggingContextFilter())  # it's that simple
        logging.basicConfig(handlers=[handler], level=logging.DEBUG)

        with context(current_file="-", current_line="-"):
            # The context above sets default value, so that the formatter does
            # not crash, when they are not defined.
            process_files(sys.argv[1:])