semvec/pypi-packages huggingface dataset:
sparkouille 0.1.6
Ways to productionize machine learning predictions
License: MIT
Keywords: sparkouille


.. _l-README:

README
======

.. image:: https://travis-ci.org/sdpython/sparkouille.svg?branch=master
    :target: https://travis-ci.org/sdpython/sparkouille
    :alt: Build status

.. image:: https://ci.appveyor.com/api/projects/status/chiwkjr9li91qd02?svg=true
    :target: https://ci.appveyor.com/project/sdpython/sparkouille
    :alt: Build Status Windows

.. image:: https://circleci.com/gh/sdpython/sparkouille/tree/master.svg?style=svg
    :target: https://circleci.com/gh/sdpython/sparkouille/tree/master

.. image:: https://badge.fury.io/py/sparkouille.svg
    :target: https://pypi.org/project/sparkouille/

.. image:: https://img.shields.io/badge/license-MIT-blue.svg
    :alt: MIT License
    :target: http://opensource.org/licenses/MIT

.. image:: https://requires.io/github/sdpython/sparkouille/requirements.svg?branch=master
     :target: https://requires.io/github/sdpython/sparkouille/requirements/?branch=master
     :alt: Requirements Status

.. image:: https://codecov.io/github/sdpython/sparkouille/coverage.svg?branch=master
    :target: https://codecov.io/github/sdpython/sparkouille?branch=master

.. image:: http://img.shields.io/github/issues/sdpython/sparkouille.png
    :alt: GitHub Issues
    :target: https://github.com/sdpython/sparkouille/issues

.. image:: https://badge.waffle.io/sdpython/sparkouille.png?label=to%20do&title=to%20do
    :alt: Waffle
    :target: https://waffle.io/sdpython/sparkouille

.. image:: http://www.xavierdupre.fr/app/sparkouille/helpsphinx/_images/nbcov.png
    :target: http://www.xavierdupre.fr/app/sparkouille/helpsphinx/all_notebooks_coverage.html
    :alt: Notebook Coverage

*sparkouille* implements a couple of ways to productionize
machine learning predictions.

*not ready*

**Links:**

* `GitHub/sparkouille <https://github.com/sdpython/sparkouille/>`_
* `documentation <http://www.xavierdupre.fr/app/sparkouille/helpsphinx/index.html>`_
* `Blog <http://www.xavierdupre.fr/app/sparkouille/helpsphinx/blog/main_0000.html#ap-main-0>`_

=======
History
=======
python-path 0.1.3
A clean way to import scripts on other folders via a context manager.
License: MIT

# Python Path
`python_path` is a simple utility that lets you cleanly add routes to your `PYTHON_PATH`. Its very useful to safely load scripts from other folders.

## Installing
You can install `python_path` from pip
```
pip install python_path
```

## Usage
Lets do an example, image you have the following project structure

```
- my_project/
  - main.py
  - some_folder/
    - other.py
    - another_folder/
      - another.py
```

Say we want to load `other.py` form `main.py`, since some_folder is not a submodule because it doesn't contain a `__init__.py` then we need to add `some_folder` to the `PYTHON_PATH`. To make this very easy we'll use `python_path` like this:

```python
# my_project/main.py

from python_path import PythonPath

with PythonPath("some_folder"):
    import other
```
and execute the file like this:
```bash
cd my_project
python main.py
```
Here `some_folder` is added relative the `PWD` (`my_project`), if you are executing `main.py` from another directory and still want to reference `some_folder`, then you should directly state relative to what file or folder the operations are being done:
```python
# my_project/main.py

from python_path import PythonPath

with PythonPath("some_folder", relative_to = __file__):
    import other
```
The previous is equivalent to:
```python
# my_project/main.py

from python_path import PythonPath
import os

path = os.path.dirname(__file__)
path = os.path.join(path, "some_folder")

with PythonPath(path):
    import other
```
Now we can also execute the script from any path and it sould still work e.g:
```bash
python my_project/main.py
```

Finally we can also navigate the folder structure by passing multiple parameters, so if we want to import `main.py` from `another.py` which is inside `another_folder` we could do it like this

```python
# my_project/some_folder/another_folder/another.py

from python_path import PythonPath

with PythonPath("..", "..", relative_to = __file__):
    import main
```
This is equivalent to
```python
# my_project/some_folder/another_folder/another.py

from python_path import PythonPath
import os

path = os.path.join("..", "..")

with PythonPath(path, relative_to = __file__):
    import main
```
extended_rospylogs 0.0.5
Extension of logs for rospy based con roscpp.
License: MIT

# Extended ROS logs for python (rospy)

`extended_rospylogs` implements for `rospy` some of the extra functionalities found in `roscpp` for logging.


## Installation

You can install `extended_rospylogs` from pip using

```
pip install extended_rospylogs
```

or using

```
pip install git+https://github.com/charlielito/extended_rospylogs
```

## ROS log messages extension
In `rospy` there are only 5 functions for logging: `rospy.logdebug`, `rospy.loginfo`, `rospy.logwarn`, `rospy.logerr` and `rospy.logfatal`. In `roscpp` you can find other options like `ROS_DEBUG_COND`, `ROS_DEBUG_NAMED`, `ROS_DEBUG_COND_NAMED`, etc (for more info go to [ros logging](http://wiki.ros.org/roscpp/Overview/Logging)).

The conditional option for logging is very useful when you want to have different logging messages in your nodes, and you want to change it in runtime (because you only can specify the `log_level` when initializing the node).

### Extended Functions
For the moment here are implemented all the `rospy` logging functions with the `cond` option:

* `logdebug_cond(bool, message)`
* `loginfo_cond(bool, message)`
* `logwarn_cond(bool, message)`
* `logerr_cond(bool, message)`
* `logfatal_cond(bool, message)`


## Usage

```python
import rospy
from extended_rospylogs import logdebug_cond, loginfo_cond


rospy.init_node('some_node')
rate = 30
debug = True
r = rospy.Rate(rate)

while not rospy.is_shutdown():

  #### DO STUFF
  logdebug_cond(debug, "Some debug message")
  loginfo_cond(debug, "Some info message for debugging")

  r.sleep()
```

Note that the `debug` variable could be a **node parameter** so it could be changed on runtime.
plumitas 0.0.1.dev3
plumitas: Pythonic analysis and visualization of Plumed output files
License: MIT
Requires Python: ~=3.6



Plumitas
========
Pythonic analysis and visualization of Plumed output files. For more
info, please go to the repository README_.

.. _README: https://github.com/UWPRG/plumitas/blob/master/README.md

License
=======
``plumitas`` is licensed under the terms of the MIT license. See the file
"LICENSE" for information on the history of this software, terms & conditions
for usage, and a DISCLAIMER OF ALL WARRANTIES.

All trademarks referenced herein are property of their respective holders.

Copyright (c) 2018--, Josh Smith, The University of Washington
Department of Chemical Engineering.