semvec/pypi-packages huggingface dataset:
promypy 0.3.0
Progressive type annotation without regression! 🚀
License: MIT
Requires Python: >=3.7

<h1 align="center">
    <strong>promypy</strong>
</h1>
<p align="center">
    <a href="https://github.com/Kludex/promypy" target="_blank">
        <img src="https://img.shields.io/github/last-commit/Kludex/promypy" alt="Latest Commit">
    </a>
        <img src="https://img.shields.io/github/workflow/status/Kludex/promypy/CI">
    <br />
    <a href="https://pypi.org/project/promypy" target="_blank">
        <img src="https://img.shields.io/pypi/v/promypy" alt="Package version">
    </a>
    <img src="https://img.shields.io/pypi/pyversions/promypy">
    <img src="https://img.shields.io/github/license/Kludex/promypy">
</p>

You've decided to add type annotation on the code source. What's your plan? 😅

This package is a small tool set to help you to achieve your dreamed fully type annotation project. 🚀

Using `mypy`, you'd probably add a [`files`](https://mypy.readthedocs.io/en/stable/config_file.html#confval-files)
entry on your configuration file, and each time someone on the team wants to include type annotation on that file,
you'd add on the `files` list. There are a some problems with this approach:

1. Each new file is not added to the `files` list.
2. If a file gets fully type annotated, you don't notice, and it will not be added to the `files` list.

The `1.` is more important, as we don't want to have regressions on our goal to have our code source fully type annotated.
But you don't want to worry about `2.` as well...

What this package does:
- [`dump`](#dump): Generates a **list** of files that are currently not type annotated.
- [`check`](#check): Given an input of files:
  - If a file is in the **list**, and is fully type annotated, it will be removed from the **list**.
  - If a file is in the **list**, and is **not** fully annotated, it will be ignored.
  - If a file is **not** in the **list**, and is fully annotated, it will be ignored.
  - If a file is **not** in the **list**, and is **not** fully annotated, it will raise errors.

## Installation

As usual.

```bash
pip install promypy
```

## Usage

There are two commands available: `dump` and `check`.

### Dump

The idea of this command is to store the list of files that are not fully type annotated into a file.

```bash
Usage: promypy dump [OPTIONS] FILES...

  Generate a list of files that are not fully type annotated.

Arguments:
  FILES...  [required]

Options:
  --mypy-args TEXT
  --output TEXT
  --help            Show this message and exit.
```

### Check

```bash
Usage: promypy check [OPTIONS] FILES...

  Check the given files with mypy, applying a set of custom rules.

Arguments:
  FILES...  [required]

Options:
  -f, --ignore-file PATH  [required]
  --mypy-args TEXT
  --help                  Show this message and exit.
```

### Pre-commit

Add the following to your `.pre-commit-config.yaml` file:

```yaml
  - repo: https://github.com/Kludex/promypy
    rev: 0.3.0
    hooks:
      - id: promypy
        args:
        - --ignore-file=<dump_filename>
```

## License

This project is licensed under the terms of the MIT license.
evmospy 1.0.2
Collection of python utils for the Evmos blockchain.
License: MIT
Requires Python: >=3.6

# Evmospy

[![PyPI version](https://badge.fury.io/py/evmospy.svg)](https://badge.fury.io/py/evmospy)

Python3.9+ utils for the Evmos Blockchain.

## Requirements

The cryptocurve dependency requires some libs to be built:

```sh
sudo apt-get install build-essential libssl-dev libffi-dev python3-dev autoconf libtool pkgconf
```

MacOS:

```sh
brew install autoconf automake libtool
```

## Installation

```sh
pip install evmospy
```

## MacOS openssl error

If you get the error that says something like `the libcrypto is running on unsafe mode` and the process is aborted:

```sh
brew install openssl
sudo ln -s /opt/homebrew/opt/openssl@1.1/lib/libcrypto.1.1.dylib /usr/local/lib
sudo ln -s /opt/homebrew/opt/openssl@1.1/lib/libssl.1.1.dylib /usr/local/lib
cd /usr/local/lib
sudo ln -s libcrypto.3.dylib libcrypto.dylib
sudo ln -s libssl.3.dylib libssl.dylib
```

## Usage

Inside each `./evmospy/<module>/` there is a README file with an example on how to use the module.