semvec/pypi-packages huggingface dataset:
agarilog 0.2.1
simple logger for message services.
License: MIT
Requires Python: >=3.7.0,<4.0.0

agarilog
========

|PyPI version| |Python Versions|

.. |PyPI version| image:: https://badge.fury.io/py/agarilog.svg
    :target: https://pypi.org/project/agarilog/
    :alt: PyPI version

.. |Python versions| image:: https://img.shields.io/pypi/pyversions/agarilog.svg
    :target: https://pypi.org/project/agarilog/
    :alt: Python versions


This is simple logger for message service.

想定用途
==========

| 長時間のバッチ処理やサービスのデモなどのloggerを想定。
| 他から呼ばれることを想定したライブラリなどには向きません。


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

.. code-block::

    pip install agarilog

Features
--------

Use .env file.
##############

.. code-block:: python

    >>> import agarilog as logger
    >>> logger.info("Hello agarilog!")

Use any .env file.
##################

.. code-block:: python

    >>> from agarilog import get_logger
    >>> logger = get_logger(name=__name__, env_file="dev.env")
    >>> logger.info("Hello agarilog!")

This is use :code:`dev.env` file.

Telegram
########

.. image:: https://github.com/sakuv2/agarilog/blob/main/img/telegram_sample.png?raw=true

Slack
#####

.. image:: https://github.com/sakuv2/agarilog/blob/main/img/slack_sample.png?raw=true

Chatwork
########

.. image:: https://github.com/sakuv2/agarilog/blob/main/img/chatwork_sample.png?raw=true

Terminal
########

.. image:: https://github.com/sakuv2/agarilog/blob/main/img/terminal_sample.png?raw=true

Environment
-----------

| 環境変数にサービスごとの設定を登録する。
| もしくは実行パスと同じ場所の :code:`.env` ファイルに記述する。
| importの方法を変えることで任意のファイルを読み込むこともできる。(上記参照)


| web系の設定は :code:`LOG_XXXX_LIMIT` を用いて並列で送信するログの数に制限をかけられる。
| 1に設定することで、ログの順序通りに送信できる。それ以上は順序は保証されない。

**Environment variables will always take priority over values loaded from a dotenv file.**

:code:`LOG_XXXX_LEVEL`: ["NOTSET", "DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"]

Telegram
########

.. code-block::

    LOG_TELEGRAM_TOKEN=XXXXXXXXX:YYYYYYYYYYYYYYYYYYYYYYYYYYYY
    LOG_TELEGRAM_CHAT_ID=XXXXXXXX
    LOG_TELEGRAM_LEVEL=WARNING # default is warning
    LOG_TELEGRAM_LIMIT=10 # default is 10

Slack
#####

.. code-block::

    LOG_SLACK_TOKEN=xxxx-YYYYYYYYYYYY-YYYYYYYYYYYY-xxxxxxxxxxxxxxxxxxxxx
    LOG_SLACK_CHANNEL=XXXXXXXXXXX
    LOG_SLACK_LEVEL=WARNING # default is warning

Chatwork
########

.. code-block::

    LOG_CHATWORK_TOKEN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    LOG_CHATWORK_ROOM_ID=XXXXXXXXX
    LOG_CHATWORK_LEVLE=WARNING # default is warning

Terminal
########

.. code-block::

    LOG_TERMINAL_TYPE=COLOR # default is COLOR
    LOG_TERMINAL_LEVEL=WARNING # default is warning

:code:`LOG_TERMINAL_TYPE`: ["NONE", "PRINT", "NORMAL", "COLOR"]


Development
-----------

| :code:`git clone` したら最初に実行すること。
| 仮想環境作成と :code:`pre-commit` のインストールが行われる。

.. code-block::

    $ make init
brt-classifier 0.1.14
A command-line tool for automatically classifying binary and ternary labelling problems on bipartite rooted trees (hence BRT).
License: MIT

# Tree classifications

This repository contains classifications of some of the problems on rooted binary trees.

## Usage

**To generage a new problem file:**

```
python -m brt_classifier generate <label-count>
```

where "label-count" is 2 or 3 will generate `problems/problems-temp.json` that contains all non-isomorphic, non-redundant problems. Moreover, it will classify some of those problems that can be automatically classified.

**To classify problems** in e.g. file `problems/3labels.json`:

```
python -m brt_classifier classify problems/3labels.json
```

Add a flag `-w` at the end, if you want the classification result's changes to persist

**To find out problems's complexity** e.g. for problem {121, 212}:

```
python -m brt_classifier find 121 212
```

Change the constraints at the end of the command to search for a different problem.

**To print statistics on a problem file** e.g. file `problems/3labels.json`:

```
python -m brt_classifier statistics problems/3labels.json
```

## Notation

_The following notation explanation is about 2-label setting, but can be trivially extended to a setting with > 2 labels_

We list the problems using sets of allowed restrictions. Since the tree is always binary, we’ll use _xyz_ as a shorthand for “if a node has a label _y_, then it must have 1 child with label _x_ and one child with label _z_”. E.g. _{ 121, 212 }_ means that if a node has label 2, it must have both children with label 1, and if a node has a label 1, it must have both children with label 2. Another example, _{112, 212, 122}_ means “if a node has label 1, it can either have children with labels 1 and 2 (i.e. children with different labels) or both children with labels 2; if a node has label 2, it must have children with 2 different labels (1, 2)”

## Problems

Note that we only consider problems that are non-isomorphic. E.g. { 112, 121 } and { 122, 212 } are isomorphic as we can just map ones to twos and twos to ones in the former instance to get to the latter one.

Besides, we also reduce the number of problems by eliminating redundant constraints wherever possible. E.g. {111, 112, 212} is in essence the same problem as {111} since 2s are never allowed to be a "parent" node. Similarly, {112, 212} is the same as {} (i.e. nothing is allowed) since 2 can never be used as a parent node so we can safely remove both 112 and 212.

### 2 labels

Most of the problems were rather trivial to classify. Lower and upper bound justifications for a not-so-trivial problem {121, 112} can be found here in [the docs folder](https://github.com/AleksTeresh/tree-classifications/tree/master/docs).

{112, 122} is O(1)-time solvable: each node simply tells one of its children "you will be 1" and the other one "you will be 2". Since {112, 122} is O(1)-time solvable then any problems that are relaxations of it are O(1)-time solvable too. Thus, {112, 212, 122} and {121, 112, 212, 122} were classified as O(1) solvable too.
flask-stub-server 0.1.5a1
This package provides the user with an easy to use endpoint generator, which that exposes endpoints that are defined through a config JSON file. Additionally, data files can be added and linked to return richer data.
License: MIT
Requires Python: >=3.9
Keywords: python stub server flask

# Simple Flask Stub Server

[![Test package with tox](https://github.com/starlord-daniel/flask-stub-server/actions/workflows/ci-pr.yml/badge.svg?branch=main)](https://github.com/starlord-daniel/flask-stub-server/actions/workflows/ci-pr.yml)

Provides the user with a Docker container, that exposes endpoints, which can be configured via json file.

## Get Started with Flask

[Documentation on the Flask website](https://flask.palletsprojects.com/en/1.1.x/installation/)

## Configure your server

The file `endpoints.json` is used to configure the server endpoints.
To learn more about the format of the configuration file, please take a look at [Configuring the server endpoints](docs/configure-endpoints.md)

Also, the [samples directory](samples/README.md) shows examples on how to configure and quickly use your own endpoint server.

## Development

This project uses a virtual environment for development.

More information can be found on the [Flask installation website](https://flask.palletsprojects.com/en/1.1.x/installation/#virtual-environments).

## Testing

For testing, this project uses `tox`. The tox.ini configures 2 environments: lint and py39.

To only run linting, use: `tox -e lint`
To only run the tests with pytest, use: `tox -e py39`

## Package

View the package [flask-stub-server on pypi](https://pypi.org/project/flask-stub-server/)

The package can be installed by running:

```bash
pip install flask-stub-server
```

To upgrade the package, use:

```bash
pip install --upgrade flask-stub-server
```