semvec/pypi-packages huggingface dataset:
RequirementsCheck 0.1.0
A CLI utility to check and update Python package versions in requirements.txt files
Requires Python: >=3.8

# Version Check

Core Functionality:
- Look for requirements*.txt files in your working directory and check for updates.
- Prompt to confirm each update with an upstream url.

## Install

RequirementsCheck is available on [pypi.org/project/RequirementsCheck/](https://pypi.org/project/RequirementsCheck/). Install into your environment with pip:

```
pip install requirementscheck
```

Add it to your `requirements.txt` file, pin the release, and use requirementscheck to update requirementscheck in your `requirements.txt` file.

## Run

From your Python project root folder run:
```
requirementscheck
```

to look for requirements files and update your dependencies based on your prompts.

Additionally, this takes to optional arguments:

- `--confirm | --no-confirm`: Ask for confirmation with link to upstream package before applying update, default `True`.
- `--pin | --no-pin`: Pin a dependency to the latest version if found to be not pinned, default `False`.
- `-h | --help`: Print help text and exit.

## Ignore

You can ignore certain lines in your requirements file by appending a comment `# rc:ignore` to the line, indicating for requirementscheck to ignore that line.

## Build

Run tests:
```
python -m unittest src/requirementscheck/test_requirementscheck.py
```

1. Update the version in setup.py
2. Git Tag
3. Push tag
4. Create release on GH
5. Build and update package to pypi:

    ```bash
    python -m build
    python -m twine upload dist/*
    ```

## Additional
Newest docs on GitHub: [bbilly1/requirementscheck](https://github.com/bbilly1/requirementscheck).
hooklet 0.5.8
An asynchronous, event-driven Python framework using NATS messaging system
Requires Python: >=3.12

# Hooklet
[![codecov](https://codecov.io/gh/yitech/hooklet/graph/badge.svg?token=3kf2NZNMKe)](https://codecov.io/gh/yitech/hooklet)


Hooklet is an event-driven framework that enables building distributed systems using message broker architecture. The v3 version centralize different data transmission models (pub/sub, req/reply) with respect to different underlying implementations. (e.g. NATS, ~~ZeroMQ~~, native Python asyncio)

## Architecture

### Core Components

1. **Pilot**
   - Abstract message broker layer
   - Predefined/Customized header support
   - Topic based data routing

2. **Node**
    - High level data transmission model base on Pilot

## Testing

Hooklet includes both unit tests and integration tests. Integration tests require a NATS server with JetStream support.

### Running Tests

```bash
# Run all tests (unit + integration, auto-starts NATS with Docker)
./scripts/test.sh all

# Run only unit tests
./scripts/test.sh unittest

# Run only integration tests (auto-starts NATS with Docker)
./scripts/test.sh integration

# Clean test caches
./scripts/test.sh clean
```

### Integration Test Requirements

Integration tests need a NATS server running on `localhost:4222` with JetStream enabled. The test script will automatically:

1. Check if NATS is already running
2. If not, start NATS using `docker-compose up -d nats`
3. Run the integration tests
4. Clean up the Docker container if it was started by the script

### Manual NATS Setup

If you prefer to manage NATS manually:

```bash
# Option 2: Using Docker directly
docker run -d --name nats-server -p 4222:4222 -p 8222:8222 nats:latest -js
```

### CI/CD

Integration tests run automatically in GitHub Actions with a hosted NATS instance for every push and pull request to the `main` branch.