semvec/pypi-packages huggingface dataset:
pyutils-v3 0.1
A handy library inspired by kaldi/egs/wsj/utils
Requires Python: >=3.7

This packages is inspired by Kaldi's utils from wsj recipe.

## utils_v3.get_stats
Recursively "walks" into data object
    and gives brief stats.
    e.g:
```
    >>> import numpy as np
    >>> import json
    >>> import utils_v3

    >>> data = [
        {'array_01':np.random.rand(3,4)},
        {'array_02':np.random.rand(3,1)}
    ]

    >>> stats = utils_v3.get_stats(data, 'data')

    >>> print(json.dumps(stats, indent=4))
    {
        "var_name": "data",
        "size": "0.078125 KB",
        "type": "<class 'list'>",
        "len": "2",
        "1st item": {
            "var_name": "data[0]",
            "size": "0.234375 KB",
            "type": "<class 'dict'>",
            "key_count": "1",
            "1st item": {
                "var_name": "data[0][array_01]",
                "size": "0.203125 KB",
                "type": "<class 'numpy.ndarray'>",
                "shape": "(3, 4)",
                "dtype": "float64"
            }
        }
    }
```
rubus-cli 1.0.9
CLI to interact with a Rubus API instance
Requires Python: >=3.6

# Rubus Client

This project contains a command-line interface program to interact
with a deployed instance of [rubus-api](https://github.com/kjuvi/rubus-api).


## Commands overview

All the commands are grouped by functionalities. Here is a quick overview of
how they are structured:

- **rubus**
    - **admin**: these commands require administrative rights
    - **authentication**: Log in and manage your user
    - **device**: manage devices (turn on/off, deployment, ...)


## Configuring the server

By default, Rubus will try to reach a running instance of Rubus API on
localhost. You can configure another address with the `RUBUS_API_URL`
environment variable.

## Authentication system

Excepted for the login, all the other commands require to be authenticated.
Rubus API works with JWT and will return you one on a successful login. Since
Rubus CLI is quite minimalist, there is no persistence, and you will have to
take advantage of your shell capabilities.

In other words, Rubus CLI will display the JWT, and prompt you to save it as an
environment variable (i.e. `RUBUS_SESSION`). The token is valid as long as your
user has not reach his expiration time (if any).

You can either set it once and for good, for example in your `.bashrc`, or just
set it in your current shell. Closing the shell will operate as a log out.
However, keep in mind that it may be accessible through the `bash_history`, in
case you are on a public computer.