semvec/pypi-packages huggingface dataset:
radge 1.3.0
A random algorithmic data generator
Requires Python: >=3.8

# Radge - Random algorithmic data generator

This simple library aims to facilitate creating testcases for and stress-testing solutions to algorithmic problems such as those found on Olympiads in Informatics, Codeforces, AtCoder, Leetcode and other sites.

## Current capabilities:
- Generating random graphs and DAGs (directed acyclic graphs)
- Generating various types of trees (random, binary, caterpillar and more)
- Generating prime numbers
- Generating sequences and permutations, with unique entries or not, sorted in any order
- Generating strings and their substrings
- Generating convex polygons

If you have any suggestions regarding any improvements or bug fixes, feel free to create an issue.
rancid-verifier 0.2.0
Rancid verifier is a tool to check [rancid's](https://shrubbery.net/rancid) `router.db` file consistency. `router.db` format is described in [router.db(5)](https://shrubbery.net/rancid/man/router.db.5.html)
Requires Python: <4.0,>=3.9

# Rancid Verifier

Rancid verifier is a tool to check [rancid's](https://shrubbery.net/rancid) `router.db` file consistency. `router.db` format is described in [router.db(5)](https://shrubbery.net/rancid/man/router.db.5.html)

## Installation

Use the package manager [pip](https://pip.pypa.io/en/stable/) to install faddr.

```bash
pip install rancid-verifier
```

## Usage

```bash
rver [path_to_routerd.db_file]
```

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License

[MIT](https://choosealicense.com/licenses/mit/)
makefile-checker 0.0.2
Package to validate makefile contents

# python-makefile-checker
Verify that scripts in your project's makefile actually exist. Use from within your GitHub actions workflow file or from python code itself!

## Context
During a development cycle, it's common for files to be renamed during the end-to-end development of a pull request
or project. Batch jobs that run make targets in python projects must have these files present in a filesystem to run
successfully, and so renames / edits to python scripts that aren't reflected in the Makefile can have unintended
consequences. It would be great to catch these errors early, before a PR is merged.

## What it does
This python project publishes a package that one can use to verify that scripts listed in a Makefile actually exist
within a filesystem. Since this utility is a script, it can be called from github actions itself, or from within
python code itself. I'll provide an example on how to use from within a GitHub Actions workflow file below.

- Finds all makefiles from within working directory, including those that are nested in subdirectories
- Validates that the scripts those makefiles specify exist
- If scripts exist within a Makefile but not within the filesystem, an exception is raised detailing which scripts are missing

## How to use

If using in a Github Actions workflow file, you can follow these steps.

### First install the package
```
pip install makefile-checker
```

## Add the following step to your workflow file:

```
  - name: Check Makefile(s)
    shell: bash
    working-directory: <your working directory>
    run: |
      poetry run check-makefile
```