semvec/pypi-packages huggingface dataset:
trikset-py-typehint 0.0.2
A package that provides type signatures to all documented methods
Requires Python: >=3.6

# trikset.py-typehint
Type hint set for TRIK

# Installing

Windows:
```
py -m pip install trik-py-typehint
```
Unix/Mac OS:
```
python3 -m pip install trik-py-typehint
```

# Usage
```python

import sys
import time
import random
import math
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from trik import *


class Program():
    __interpretation_started_timestamp__ = time.time() * 1000

    pi = 3.141592653589793

    def execMain(self):

        brick.display().addLabel("Hi from typed TRIK Python!", 1, 1, 20)
        brick.display().redraw()

        brick.stop()
        return

    def main():
        program = Program()
        program.execMain()

if __name__ == '__main__':
    main()
```
boaviztapi-test 0.0.7
Giving access to BOAVIZTA referenced datas and methodologies trought a RESTful api
Requires Python: >=3.7
Keywords: boavizta,api

# BOAVIZTAPI [![Python tests main](https://github.com/Boavizta/Tools-API/actions/workflows/main-main.yml/badge.svg?branch=main)](https://github.com/Boavizta/Tools-API/actions/workflows/main-main.yml)

Giving access to BOAVIZTA referenced datas and methodologies trought a RESTful API

## :dart: Objective

As part of Boavizta's desire to improve the quality of the measurement of the environmental impacts of ICTs in organizations, this project aims at giving access to the group's work to as many people as possible in an automated and industrialized way.  

The various data and methodologies integrated by Boavizta are aggregated and made available via an API. 

In the interest of transparency and scientific popularization, the opening of the code, the versioning of the impact factors and the documentation of the project are critical points.

The system is developed in layers according to a bottom-up principle. The first layer implemented is equipment, starting with the servers (MVP). The second layer is the measurement of the impact of digital services or systems. The measurement of the global impact is currently outside the scope. 

## :fast_forward: Test it yourself

* Test the API : http://149.202.161.61:5000/docs

* Dev documentation server : http://149.202.161.61/

* Dev API server: http://149.202.161.61:5000

## :computer: Setup project locally with pipenv

### Setup pipenv

Install pipenv globally
```bash
$ sudo pip3 install pipenv
```

Install dependencies and create a python virtual environment.
```bash
$ pipenv install -d 
$ pipenv shell
```

### Launch a development server

**Once in the pipenv environment**

Development server uses [uvicorn](https://www.uvicorn.org/) and [fastapi](https://fastapi.tiangolo.com/), you can launch development server with the `uvicorn` CLI.

```bash
$ uvicorn boaviztapi.main:app --host=localhost --port 5000
```
You can run the tests with `pytest`.

### API Swagger

Once API server is launched API swagger is available at [http://localhost:5000/docs](http://localhost:5000/docs).

## :whale: Install using docker container
```bash
$ docker run ghcr.io/boavizta/boaviztapi:latest
```

## 📦 Install using pip package
```bash
$ pip3 install boaviztapi
```

## :woman: Contributing

See [contributing.md](./CONTRIBUTING.md)

You can build a source distribution (installable with pip) with `python setup.py sdist`.

## :one: Versionning

We use [Semantic Versioning 2.0.0](https://semver.org/)

|    Type     | Description                                                          |    Command        |
| :---        |    :----:                                                            |              ---: |
| MAJOR       | version when you make incompatible API changes                       | ```make major```  |
| MINOR       | version when you add functionality in a backwards compatible manner  | ```make minor```  |
| PATCH       | version when you make backwards compatible bug fixes                 | ```make patch```  |

## :scroll: License

TODO
encode-utils 2.11.0
Client and tools for ENCODE data submitters.

© 2019 The Board of Trustees of the Leland Stanford Junior University.

# encode_utils
Tools that are useful to any ENCODE Consortium submitting group, as well as the general community working with ENCODE data.  Library and scripts are coded in Python.

See the [wiki](https://github.com/StanfordBioinformatics/encode_utils/wiki) to get started. 

API and script documentation are available on [Read the Docs](http://encode-utils.readthedocs.io/en/latest/).


# Latest news

Oct. 28, 2019

Release [2.8.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.8.0)

***

Apr. 11, 2019

Release [2.7.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.7.0)

***

Jan. 11, 2019

Release [2.6.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.6.0)

***

Nov. 15, 2018

Now available on [PyPI](https://pypi.org/project/encode-utils) with ``pip install encode-utils``.

***

Nov. 2, 2018

Release [2.5.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.5.0)

***

Oct. 11, 2018

Release [2.4.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.4.0)

***

Aug 9, 2018

Release [2.3.1](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.3.1).
Adds support to transfer from S3 to GCP (see release notes from [2.3.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/2.3.0)). 

***

Jun 15, 2018

Release [1.5.2](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.5.2)

***

June 7, 2018

Release [1.5.1](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.5.1)

***

May 21, 2018

Release [1.5.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.5.0)

***

May 10, 2018

Release [1.4.1](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.4.1)

***

May 4, 2018

Release [1.4.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.4.0).

***

Apr. 5, 2018

Release [1.3.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.3.0). 

***

Apr. 3, 2018

Release [1.2.1](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.2.1).

***

Mar. 26, 2018

Release [1.2.0](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.2.0).

***

Feb. 23, 2018

Release [1.1.3](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.1.3).

***

Feb. 15, 2018

Release [1.1.1](https://github.com/StanfordBioinformatics/encode_utils/releases/tag/1.1.1).

***

Feb. 12, 2018

Release [1.0.0](https://github.com/StanfordBioinformatics/encode_utils/tree/1.0.0).
saiblo-local-judger 0.0.2
Saiblo Local Judger
Requires Python: >=3.7

# Saiblo Local Judger (Exp)

实验版的Saiblo本地调试用评测机。

## Overview

1. Core核心：使用TCP Socket提供本地AI连接与游戏运行支持，和Saiblo上的Judger保证行为相同。同时提供了CLI接口。
2. GUI：提供选手易于使用的图形界面
3. AI Adapter：为未支持的AI提供原始协议和TCP协议的转发，但是仍然建议新的游戏的ADK直接提供相关支持

## 核心运行流程

1. 读取提供的游戏配置，其中可能包含
   1. 游戏人数
   2. 游戏逻辑路径
   3. 游戏配置
   4. 通讯协议版本
2. 在随机端口启动本地TCP Socket服务器，并等待AI连接。
3. 全部AI均已成功连接后，启动游戏逻辑
4. 按照 [Saiblo 文档](https://docs.saiblo.net/developer/developer.html) 运行游戏流程