semvec/pypi-packages huggingface dataset:
animedata 0.3.9
Open-source library containing package about animes/series and including a built-in utility.
Requires Python: >=3.11

# AnimeData

## Presentation

AnimeData is a python-based project developed by swarthur.

The project's goal is to offer an open-source and easy way to get data about its favourite animes and series.

AnimeData is composed of 2 main files :

1. *animedata.py* : Python module essential to exploit and modify the JSON database.
2. *animedata_source.json* : JSON file : series database.

## Data available

Some data about an anime may be missing, especially if the anime has been added a long time ago. However, each anime should be compatible with the latest version of AnimeData.

## How to use this library

In order to make this project useful for everyone, anybody can use the provided tool to get, add or modify its animes or series, **from a compatible manager**.
> Currently, only AnimeTime is compatible with showdata.

### How does the tool works ?

The tool's input needs to be an dictionnary, specially formatted, with special keys provided in a dictionnary in the module.

Example of formatted python dictionnary :

```py
json_dict = {"anime_name":{
    "seasons_episodes":{
        "episode_number":{
            "episode_name" : "episode_name",
            "episode_duration" : 00,
            "episode_release_date" : [MM,DD,YYYY]
            }
        ...} # Others episodes
        }
    ...} # Others series 
```

### Does another JSON file is compatible ?

AnimeData uses metadata, and corruped metadata stops the tool from loading the data.

The AnimeData loading-friendly files are :

* animedata_source.json : source file of the database
* animedata_local.json : custom file, similar to the source file but containing custom data from an series manager.

The AnimeData saving-friendly files is:

* animedata_local.json : custom file used to save anime's custom data from a compatible anime manager.
pdf-cleanup-empty 0.0.1
This package can be used to remove white/empty pages from a pdf.
Requires Python: >=3.8

# pdf_cleanup_empty

This package can be used to remove white/empty pages from a pdf.

## Usage

Install via pip

    $ pip install pdf_cleanup_empty
  
Use via CLI

    $ cleanup --help
    Usage: cleanup [OPTIONS] [INPUT_PATH]...

    Removes empty and blank pages from the provided pdf files and saves them
    with the suffix _clean.

    Options:
    -t, --target PATH  Provide a target path where the newly create files will
                        be saved.
    -v, --verbose      Show some details while processing the documents.
    --help             Show this message and exit.
firegs 0.9
A tool to add app to Firebase project from the command line

# FireGS

FireGS is a command-line tool for managing Firebase Android Apps. It allows you to create new apps and list all apps in your Firebase project.

## Installation

You can install FireGS using pip:

```bash
pip install firegs
```

You will also need to provide the path to your Firebase service account key file. You can do this by running the `firegs` command:

```bash
firegs
```

This will prompt you for the path to your service account key file.

## Usage

To create a new Firebase Android app, run the `firegs` command with the `-c` flag followed by the package name of the new app. You can also provide a display name for the app with the `-d` flag:

```bash
firegs -c com.example.app -d "Example App"
```

To list all Firebase Android apps in your project, run the `firegs` command with the `-l` flag:

```
firegs -l
```

## License

FireGS is released under the MIT License. See the LICENSE file for more details.
Loden-9000 1.0.0
Making faces, in time.
Requires Python: >=3.6

# Loden
Evolving to support a huge farm of display devices, the goal is to manage a "sea of green" visualization for colorized grids.

Core abstractions support grids as well as command-line processing. Target platforms are decidedly GUI, as well as TUI.

Grids support in-cell text, cell-based metrics, command line events, as well as a scripting-worthy CLI.

The CLI is in [GridCommander.py](https://github.com/Python3-Training/Loden/blob/main/Loden1/GridCommander.py).

Feel free to also open + run [GridTK.py in Loden1](https://github.com/Python3-Training/Loden/blob/main/Loden1/GridTK.py) to see how to make some faces, just 'in time' ...

![The Tk Demonstration](https://github.com/Python3-Training/Loden/blob/main/_images/DefaultDemo.png)

## zSupport?
If you want to support the effort, I seek no donations. Instead, simply feel free to purchase one of [my educational](https://www.udemy.com/user/randallnagy2/) or [printed](https://www.amazon.com/Randall-Nagy/e/B08ZJLH1VN?ref=sr_ntt_srch_lnk_1&qid=1660050704&sr=8-1) productions?
hatch-build-scripts 0.0.4
A plugin for Hatch for writing build scripts
Requires Python: >=3.9

# Hatch Build Scripts

A plugin for [Hatch](https://github.com/pypa/hatch) that allows you to run arbitrary
build scripts and include their artifacts in your package distributions.


## Installation

To set up `hatch-build-scripts` for your project you'll need to configure it in your
project's `pyproject.toml` file as a `build-system` requirement:

```toml
[build-system]
requires = ["hatchling", "hatch-build-scripts"]
build-backend = "hatchling.build"
```

## Usage

Now you'll need to configure the build scripts you want to run. This is done by adding
an array of scripts to the `tool.hatch.build.hooks.build-scripts.scripts` key in your
`pyproject.toml` file. Each script is configured with the following keys:

| Key | Default | Description |
| --- | ------- | ----------- |
| `commands` | required | An array of commands to run. Each command is run in a separate shell. |
| `artifacts` | required | An array of artifact patterns (same as `.gitignore`) to include in your package distributions. |
| `out_dir` | `"."` | The directory to copy artifacts into. |
| `work_dir` | `"."` | The directory to run the commands in. All artifact patterns are relative to this directory. |
| `clean_artifacts` | `true` | Whether to clean files from the `out_dir` that match the artifact patterns before running the commands. |
| `clean_out_dir` | `false` | Whether to clean the `out_dir` before running the commands. |

In practice this looks like:

```toml
[[tool.hatch.build.hooks.build-scripts.scripts]]
out_dir = "out"
commands = [
    "echo 'Hello, world!' > hello.txt",
    "echo 'Goodbye, world!' > goodbye.txt",
]
artifacts = [
    "hello.txt",
    "goodbye.txt",
]

[[tool.hatch.build.hooks.build-scripts.scripts]]
# you can add more scripts here...
```

You can configure script defaults for scripts by adding a `[tool.hatch.build.hooks.build-scripts]` table to your `pyproject.toml` file. The following keys are supported:

| Key | Default | Description |
| --- | ------- | ----------- |
| `out_dir` | `"."` | The directory to copy artifacts into. |
| `work_dir` | `"."` | The directory to run the commands in. All artifact patterns are relative to this directory. |
| `clean_artifacts` | `true` | Whether to clean files from the `out_dir` that match the artifact patterns before running the commands. |
| `clean_out_dir` | `false` | Whether to clean the `out_dir` before running the commands. |