semvec/pypi-packages huggingface dataset:
csboilerplate 0.1.0
console script boilerplate
License: MIT
Keywords: cli console commandline

console script boilerplate
==

some boilerplate stuff for console scripts. inspired by now unmaintained `pyCLI`.

decorate your main function and register it in your `setup.py` as `console_scripts`
entry_point [1]. the function will receive an app object as argument.

you get:
- pythons `ArgumentParser`
- `KeyboardInterrupt` is catched
- `SIGTERM` is handled, so that context managers will exit properly
- logging helper

`exit_handler` and `sigterm_handler` may be customized.

[1] <https://setuptools.readthedocs.io/en/latest/setuptools.html#automatic-script-creation>


example
--

```python
from csboilerplate import cli_app


@cli_app(name=__name__)
def main(app):
    app.logging_config(log_level=app.args.debug)
    # do your stuff


main.argparser.add_argument('-d', '--debug', action='count', default=0,
                            help='lower logging threshold, may be used twice')
```


dev env
==

checkout git and:

```commandline
virtualenv .env -p python3
. .env/bin/activate
pip install -e .[dev]
```
simple-pinq 1.0.1
LINQ style API for Python.
License: MIT
Keywords: linq pinq api

# pinq
A [LINQ](https://msdn.microsoft.com/en-us/library/bb308959.aspx) style API for Python iterables. Inspired by [JINQ](https://github.com/VivekRagunathan/JINQ).

## Installation
```
pip install simple-pinq
```

## Docs
These are a work in progress. For now, check out the [unit tests](./tests).

## Tests
[![Build Status](https://travis-ci.org/tizz98/pinq.svg?branch=master)](https://travis-ci.org/tizz98/pinq)
When contributing, make sure the test code coverage is not below 100%. To run tests:
```
pip install -e .
pytest tests --cov=pinq
flake8 pinq tests
```
Tree 0.2.4
A package for creating and drawing trees
License: MIT

PyTree
======
.. image:: https://img.shields.io/pypi/v/tree.svg?style=flat-square
        :target: https://pypi.python.org/pypi/Tree

.. image:: https://img.shields.io/pypi/l/Tree.svg?style=flat-square
        :target: https://github.com/PixelwarStudio/PyTree/blob/master/LICENSE

Python package, which you can use to generate and drawing trees, realistic or fractal ones.

Usage
-----
.. code-block:: bash

    $ pip install Tree

.. code-block:: python

    from math import pi, radians as rad
    from Tree.core import Tree
    from PIL import Image

    branches = (
        (.5, rad(-30)),
        (.6, rad(30)),
        (.4, rad(60))
    )

    def main():
        tree = Tree(
            pos=(0, 0, 0, -500),
            branches=branches
        )
        
        # Let the tree grow
        tree.grow(10)
        
        # Move the tree in the right position, so that the tree is completly in the image
        tree.move_in_rectangle()

        im = Image.new("RGB", tree.get_size(), (239, 239, 239))
        tree.draw_on(im, (85, 25, 0, 128, 53, 21), (0, 62, 21), 10)
        im.show()

    if __name__ == '__main__':
        main()
    
.. image:: https://raw.githubusercontent.com/PixelwarStudio/PyTree/master/images/example.png

Documentation
-------------
The documentation is hosted on Readthedocs_.

.. _Readthedocs: http://pytree.readthedocs.io/en/latest/
jupyter-remote 0.9.3
Run Jupyter on a remote server
License: MIT
Keywords: jupyter,remote,ssh,slurm,pexpect,orchestra,o2

==============
Jupyter-Remote
==============

`Jupyter-Remote <https://github.com/aaronkollasch/jupyter-remote>`_
is a command-line tool that automatically runs Jupyter on a remote server.
It is derived from `Jupyter-O2 <https://github.com/aaronkollasch/jupyter-o2>`_.

Jupyter-Remote aims to streamline remote Jupyter usage for a range of remote configurations,
from simple servers to SLURM clusters that require request forwarding to a compute node.

Installation
------------------------------

Set up Jupyter on the remote server.

Next, install Jupyter-Remote.

.. code-block:: console

    pip install jupyter-remote

Then, generate the config file.

.. code-block:: console

    jupyter-remote --generate-config

Follow the printed path to ``jupyter-remote.cfg`` and edit to suit your needs.

For more info on setting up Jupyter and troubleshooting Jupyter-Remote, see the `jupyter-remote tips`_.

.. _jupyter-remote tips: https://github.com/aaronkollasch/jupyter-remote/blob/master/jupyter_remote_tips.rst

Usage
------------------------------

.. code-block:: console

    jupyter-remote [profile] [subcommand]

Both arguments are optional.

If Jupyter is installed on your machine, Jupyter-Remote can be run as a Jupyter subcommand:

.. code-block:: console

    jupyter remote o2 lab

Be sure to try out `JupyterLab <https://github.com/jupyterlab/jupyterlab>`__!

For more info on the Jupyter-Remote command-line options, use ``jupyter-remote --help``.

Profiles
------------------------------
Make a copy of ``jupyter-remote.cfg`` and name it ``jupyter-remote-[profile name].cfg``.
See ``example_cfgs/jupyter-remote-o2.cfg``.

Note: Both the profile and subcommand option are optional.
If only one is provided, Jupyter-Remote will first look for a profile with that name,
and if none is found, it will use the default profile with the given subcommand.

Requirements and compatibility
------------------------------
* python 2.7 or 3.6
* pexpect.pxssh
* POSIX: Jupyter-Remote has been tested on MacOS and Linux, while on Windows it will
  require Cygwin and Cygwin's version of Python.
* pinentry (suggested)