semvec/pypi-packages huggingface dataset:
ttsdb-core 0.1.4
Core package for TTSDB systems - base classes for voice cloning TTS models.
Requires Python: >=3.8

## `ttsdb-core`

`ttsdb-core` provides the shared “adapter” surface that every model package implements.

### Key pieces

- **`VoiceCloningTTSBase`**: abstract base class for voice-cloning style TTS adapters.
  - Subclasses implement `_load_model()` and `_synthesize()` and use `synthesize()` for the public API.
- **`ModelConfig`**: helper for loading a model package’s bundled `config.yaml` (supports editable installs too).
- **Vendoring utilities**: helpers to make upstream research code importable at runtime:
  - `setup_vendor_path(package_name)`: prepends `src/<pkg>/_vendor/source[/code.root]` to `sys.path`
  - `vendor_context(...)`: optional context manager for research code that assumes a working directory or env vars

### Model package conventions

Each model package lives in `models/<name>/` and typically includes:

- `pyproject.toml`: packaging metadata (including `requires-python`)
- `config.yaml`: model metadata + dependency constraints + pointers to upstream code/weights
- `src/ttsdb_<name>/__init__.py`: the adapter implementation
- `tests/`: lightweight unit tests and optional `integration` tests (weights required)

### Python version constraints

Because upstream research code often depends on specific Python versions, model packages express **supported Python versions** in two places:

- `pyproject.toml` → `requires-python` (PEP 440 specifier string)
- `config.yaml` → `dependencies.python` (same specifier string)

For local development automation, `config.yaml` may also include:

- `dependencies.python_venv`: a concrete interpreter version used by `just setup` when creating a venv
- `dependencies.python_tested`: optional explicit list of tested interpreters (human-facing)
zdev 0.2.1
Versatile collection of helper functions for common development tasks
Requires Python: >=3.12
Keywords: development, utilities, helpers

# zdev

Versatile collection of helper functions for common development tasks.

## Synopsis

This library provides handy functions for frequent tasks during development as well as for productive use in Python programs (e.g. stripping fileparts). Application focus is to support **automation scripts** as well as development of **algorithmic functions**.

## Contents

The package is structured into the following modules:  

- **colors**: Default color definitions w/ semantic names, e.g. 'cRed' or 'cDodgerBlue'

- **core**: Basic type & file checking helpers.

- **display**: Handy convenience functions for a one-line, yet sophisticated, control of figures based on ```matplotlib``` and ```plotly``` calls. *Note: For support on plotting ```zynamon.zeit.TimeSeries``` the underlying package must be installed as well! (optional requirement)*

- **indexing**: Helpers related to all kinds of "find-something" tasks (e.g. file-goto, runlength sections etc)

- **parallel**: Convenience functions for Python's builtin ```multiprocessing``` package and custom classes for controllable dispatching of jobs onto N cores.

- **searchstr**: Regular expressions to find common strings (e.g. identifiers w/ or w/o hyphens, numbers etc)
  
- **sound**: Audio-related helpers (e.g. interpret any array and play as sound w/ defined fs)

- **testing**: Set of dummy functions w/ and w/o arguments and possible writing of "flag-files" that can be used for testing of e.g. routines in ```zdev.parallel```

- **utils**: Main collection of frequently used dev utilitites (e.g. dependency analysis, bulk file operations, infos on storage/time/etc)

- **validio**: Functions to check & convert for a robust I/O behaviour (e.g. auto-replace "problematic" characters etc)

[ Dr. Marcus Zeller | dsp4444@gmail.com | Erlangen, Germany | 2019-2026 ]
hallu-assess 0.1.0
Measure how much an LLM’s answers drift to detect hallucination risk and improve prompts for more reliable results.
Requires Python: >=3.9

# hallu-assess

Measure how much an LLM’s answers drift to detect hallucination risk and improve prompts for more reliable outputs.

## What it does

`hallu-assess` evaluates hallucination risk by:
- running the same prompt multiple times
- embedding each response
- measuring semantic deviation across outputs

High deviation → higher hallucination risk.

## Installation

```bash
pip install hallu-assess
```
## Detailed Documentation - WIP
bottle-cli 0.1.0
Get human feedback on your projects - message in a bottle for developers
Requires Python: >=3.9
Keywords: cli, code-review, developer-tools, feedback

# 🍾 Bottle CLI

Get human feedback on your projects. Message in a bottle for developers.

## Install

```bash
pip install bottle-cli
```

## Usage

```bash
# Submit your project (costs 1 token)
bottle submit

# Review others (earn 0.5 tokens)
bottle review

# Check your feedback
bottle inbox

# Check token balance
bottle tokens
```

That's it. First run asks for your Gemini API key (free from aistudio.google.com).

## How It Works

```
You                          Other Devs
 │                               │
 ├── bottle submit ────────────► Pool
 │   (costs 1 token)             │
 │                               │
 │   ◄──────────── bottle review ┤
 │                 (earns 0.5)   │
 │                               │
 └── bottle inbox                │
     (see feedback)              │
```

## Token Economy

| Action | Tokens |
|--------|--------|
| Start | +3 free |
| Submit | -1 |
| Review | +0.5 |
| Get thumbs up | +0.5 bonus |

## For Package Maintainers

If you're forking/hosting your own version:

### 1. Supabase Setup
```bash
# Create project at supabase.com
# Run schema.sql in SQL Editor
# Copy URL + anon key (NOT service_role!)
```

### 2. Update Code
```python
# In bottle_cli/__init__.py
SUPABASE_URL = "https://your-project.supabase.co"
SUPABASE_ANON_KEY = "eyJ..."
```

### 3. Publish
```bash
pip install build twine
python -m build
twine upload dist/*
```

## License

MIT