fauxdata-cli 0.2.0__tar.gz → 0.2.1__tar.gz

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fauxdata-cli
-Version: 0.2.0
+Version: 0.2.1
 Summary: CLI for generating and validating fake datasets
 Project-URL: Homepage, https://aborruso.github.io/fauxdata/
 Project-URL: Repository, https://github.com/aborruso/fauxdata
@@ -13,7 +13,7 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.11
-Requires-Dist: pointblank>=1.0.1
+Requires-Dist: pointblank>=1.1.0
 Requires-Dist: polars>=1.0
 Requires-Dist: pyfiglet>=1.0
 Requires-Dist: pyyaml>=6.0
@@ -93,7 +93,7 @@ fauxdata init --name orders
 
 ## Schema format
 
-A schema is a YAML file that describes the structure of your dataset. Here is a realistic example for a people dataset:
+A schema is a YAML file that describes the structure of your dataset. Here is a realistic example for a people dataset, adapted from [`schemas/people.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/people.yml):
 
 ```yaml
 name: people
@@ -365,13 +365,13 @@ fauxdata validate data.csv schema.yml --json
 
 ## Example schemas
 
-Three ready-to-use schemas are included in `schemas/`:
+Three ready-to-use schemas are included in [`schemas/`](https://github.com/aborruso/fauxdata/tree/main/schemas):
 
 | Schema | Domain | Columns |
 |--------|--------|---------|
-| `people.yml` | Personal data | id, name, email, age, city, country_code, active, signup_date, score |
-| `orders.yml` | E-commerce | order_id, customer_id, product, amount, status, created_at |
-| `events.yml` | Analytics | event_id, user_id, event_type, timestamp, ip, user_agent, session_duration |
+| [`people.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/people.yml) | Personal data | id, name, email, age, city, country_code, active, signup_date, score |
+| [`orders.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/orders.yml) | E-commerce | order_id, customer_id, product, amount, status, created_at |
+| [`events.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/events.yml) | Analytics | event_id, user_id, event_type, timestamp, ip, user_agent, session_duration |
 
 ---
 

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/README.md

@@ -69,7 +69,7 @@ fauxdata init --name orders
 
 ## Schema format
 
-A schema is a YAML file that describes the structure of your dataset. Here is a realistic example for a people dataset:
+A schema is a YAML file that describes the structure of your dataset. Here is a realistic example for a people dataset, adapted from [`schemas/people.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/people.yml):
 
 ```yaml
 name: people
@@ -341,13 +341,13 @@ fauxdata validate data.csv schema.yml --json
 
 ## Example schemas
 
-Three ready-to-use schemas are included in `schemas/`:
+Three ready-to-use schemas are included in [`schemas/`](https://github.com/aborruso/fauxdata/tree/main/schemas):
 
 | Schema | Domain | Columns |
 |--------|--------|---------|
-| `people.yml` | Personal data | id, name, email, age, city, country_code, active, signup_date, score |
-| `orders.yml` | E-commerce | order_id, customer_id, product, amount, status, created_at |
-| `events.yml` | Analytics | event_id, user_id, event_type, timestamp, ip, user_agent, session_duration |
+| [`people.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/people.yml) | Personal data | id, name, email, age, city, country_code, active, signup_date, score |
+| [`orders.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/orders.yml) | E-commerce | order_id, customer_id, product, amount, status, created_at |
+| [`events.yml`](https://github.com/aborruso/fauxdata/blob/main/schemas/events.yml) | Analytics | event_id, user_id, event_type, timestamp, ip, user_agent, session_duration |
 
 ---
 

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "fauxdata-cli"
-version = "0.2.0"
+version = "0.2.1"
 description = "CLI for generating and validating fake datasets"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -13,7 +13,7 @@ classifiers = [
     "Operating System :: OS Independent",
 ]
 dependencies = [
-    "pointblank>=1.0.1",
+    "pointblank>=1.1.0",
     "typer>=0.12",
     "rich>=13",
     "pyfiglet>=1.0",
@@ -46,3 +46,6 @@ build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/fauxdata"]
+
+[tool.hatch.build.targets.sdist]
+only-include = ["src", "tests", "schemas", "README.md", "LICENSE", "pyproject.toml"]

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/src/fauxdata/__init__.py

@@ -1,3 +1,3 @@
 """fauxdata - CLI for generating and validating fake datasets."""
 
-__version__ = "0.2.0"
+__version__ = "0.2.1"

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/src/fauxdata/commands/agent.py

@@ -139,7 +139,7 @@ Notes:
 
 {presets}
 
-Presets are locale-aware and coherent within a row (the email matches the name, the city matches the country). Known limit: `unique: true` is not enforced on person and address presets such as `name`, `email`, `user_name`, `city` (pointblank issue #441). Validate with `rows_distinct` if uniqueness matters.
+Presets are locale-aware and coherent within a row (the email matches the name, the city matches the country).
 
 ## Validation rules
 

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/src/fauxdata/validator.py

@@ -80,8 +80,7 @@ def _add_rule(v: pb.Validate, rule: ValidationRule) -> None:
 
 def _extract_results(v: pb.Validate, rules: list[ValidationRule]) -> list[dict]:
     """Extract per-step results as a list of dicts."""
-    # validation_info, not get_dataframe_report(): the report fails on list-valued
-    # columns (rows_distinct) in pointblank 1.0.1
+    # validation_info carries active and eval_error, used to flag steps that could not run
     steps = {s.i: s for s in v.validation_info}
     results = []
     # Build a flat list of steps (one per column for multi-column rules)

{fauxdata_cli-0.2.0 → fauxdata_cli-0.2.1}/tests/test_generator.py

@@ -103,6 +103,15 @@ def test_generate_float_precision_stays_in_range():
     assert df["f"].max() <= 9.999
 
 
+def test_generate_unique_coherent_presets():
+    """unique is enforced on coherent presets (pointblank >= 1.1.0, posit-dev/pointblank#441)."""
+    schema = _make_schema([ColumnSchema(name="name", col_type="string", preset="name", unique=True),
+                           ColumnSchema(name="email", col_type="string", preset="email", unique=True)])
+    df = generate_dataset(schema, rows=2000, seed=1)
+    assert df["name"].n_unique() == 2000
+    assert df["email"].n_unique() == 2000
+
+
 def test_generate_float_precision_unique():
     """A unique float column stays unique after rounding."""
     schema = _make_schema([ColumnSchema(name="f", col_type="float", min=0.0, max=1.0,

fauxdata_cli-0.2.0/.python-version

@@ -1 +0,0 @@
-3.12

fauxdata_cli-0.2.0/LOG.md

@@ -1,84 +0,0 @@
-# Log
-
-## 2026-10-11 — 0.2.0 (non rilasciata): pointblank 1.0.1, `precision` nativa, `col_vals_str_len`, fix, comando `agent` e `--json`
-
-- Bump `pointblank>=1.0.1` (da 0.25.0). 103/103 test invariati; schemi inclusi PASS; stesso seed → CSV identici byte per byte tra 0.25 e 1.0.1. Effetto collaterale: da 0.27 pointblank richiede `anthropic[bedrock]` → 20 pacchetti in più installati (anthropic, boto3, pydantic, …), non usati da fauxdata.
-- `precision` float: ora nativa (`pb.float_field(precision=)`), unicità garantita dopo l'arrotondamento. Limiti stretti verso l'interno sulla griglia dei decimali (`max: 9.999`, `precision: 2` → `9.99`) perché l'arrotondamento non sfori il range; errore chiaro se nessun valore ci sta. Documentata nel README (prima non lo era).
-- Nuova regola `col_vals_str_len` (`column`, `min`/`max`, null ignorati). `infer` la emette solo per stringhe libere: su preset/pattern/values il generatore ignora le lunghezze.
-- Fix: le regole sui valori (`between`, `gt/lt/ge/le`, `regex`, `in_set`) ignorano i null (`na_pass=True`; `in_set` via `None` nel set). Prima una colonna col 20% di null falliva 195/1000 righe.
-- Fix: `infer --categorical-threshold` da CLI arrivava come float (anche il default) e pointblank lo leggeva come frazione → ogni colonna stringa senza preset diventava categorica con i valori reali copiati in `values:`. Ora gli interi ≥ 1 passano come conteggio.
-- Fix: `values` sulle colonne `int`/`float` ora rispettato in generazione (passato come `allowed`); prima `infer` lo emetteva per gli int a bassa cardinalità e il generatore lo ignorava (403/500 fallimenti in round-trip).
-- Fix: `rows_distinct` esclude le righe con null nelle colonne controllate (come SQL UNIQUE); prima i null contavano come duplicati tra loro.
-- Bug di pointblank (non nostro): `unique=True` ignorato sui preset coerenti (`email`, `name`, `city`, …); segnalato in https://github.com/posit-dev/pointblank/issues/441. Non corretto: `unique` + `nullable` su range stretto non generabile.
-- Nuovo comando `fauxdata agent`: guida Markdown per agenti AI (flusso, output JSON, exit code, schema, tipi, preset, regole, esempio); liste generate dalle costanti di `schema.py`.
-- Nuovo flag `--json` su `generate`, `validate`, `infer`, `preview`: stdout contiene solo un oggetto JSON; errori come `{"error": ...}` con exit 1. Sezione README "Using fauxdata with AI agents".
-- Fix: un passo su una colonna assente dal dataset risultava `ok: true` con 0/0 righe; ora campo `evaluated` (da `validation_info`), `ok: false`, `NOT RUN` in tabella. `get_dataframe_report()` non usabile: fallisce con `rows_distinct`/`rows_complete` + `columns_subset` (segnalato in https://github.com/posit-dev/pointblank/issues/442). Chiude la issue #1 di fauxdata (output strutturato → `--json`).
-- Sito `docs/index.html`: badge pointblank 1.0+, "six commands", righe `infer` e `agent`, `--json`.
-- 143/143 test, coverage 87.05%.
-
-## 2026-07-04 — v0.1.6
-
-- Release `0.1.6`: include il fix issue #2 (`precision` float). Build con `uv build`, tag `v0.1.6`.
-- Deploy PyPI **manuale** (`uv publish`): nessun workflow di release automatico.
-
-## 2026-07-04 — fix issue #2: `precision` float ignorato
-
-- Bug: l'opzione `precision` dei float veniva letta nello schema ma mai applicata (`pb.float_field` non ha il parametro). Valori generati con precisione piena.
-- Fix in `generator.py`: dopo `pb.generate_dataset`, arrotondo con `pl.col(...).round(precision)` le colonne `float` con `precision` impostato.
-- Verifica: reproducer della issue → output atteso (`27.74, 169.64, …`). Test `test_generate_float_precision`. 103/103 pass.
-
-## 2026-06-12 — pointblank 0.25 + comando `infer`
-
-- Bump `pointblank>=0.25` (uscito su PyPI). Schemi inclusi (people/orders/events) verificati: tutti PASS.
-- Fase B regressioni: `rows_distinct` ora include righe con null (correttezza migliorata), lazy frame ok. fauxdata passa sempre DataFrame eager → nessun impatto.
-- Nuovo comando **`fauxdata infer DATASET`**: da tabella reale (csv/parquet/json/jsonl) genera schema YAML (`columns:` + `validation:`) via `pb.schema_from_tbl`. Flag: `--out/-o`, `--name/-n`, `--rows/-r`, `--format/-f`, `--categorical-threshold`, `--detect-presets/--no-detect-presets`, `--sample-size`.
-- `ColumnSchema`: nuovi campi `min_length`/`max_length` per stringhe (round-trip fedele); passati a `pb.string_field`. Validazione parsing (negativi, min>max).
-- infer CSV: `try_parse_dates=True` → date/datetime tipizzati invece che congelati come categorici.
-- generate: errore chiaro su conflitto unique+range stretto ("too narrow a range") invece del traceback criptico di pointblank.
-- Limite noto: colonne a bassa cardinalità congelate ai valori reali (possibile leak su colonne sensibili) — documentato nel README.
-- Test: +14 (`tests/test_infer.py` + length in `test_new_fields.py`). 102/102 pass, coverage 83.2%.
-
-- `init`: aggiunto `--description`, `--rows`, `--format`, `--yes`; questionary diventa fallback
-- Tutti i comandi: `epilog` con esempi in `--help`
-- `generate`: aggiunto `--dry-run` (mostra piano senza scrivere)
-- `generate`: output su successo mostra `output_path`, `format`, `rows` come chiave: valore
-- `init`: output su successo aggiunge `schema_path: <file>`
-- Fix venv: ricreato con `uv venv --clear` (cartella rinominata da `real_fake_datasets`)
-
-## 2026-03-06 — v0.1.3
-
-- Add Python classifiers to pyproject.toml (3.11, 3.12, 3.13, MIT) — fixes pyversions badge
-- Fix version tests to read `__version__` dynamically instead of hardcoded string
-
-## 2026-03-06 — v0.1.2
-
-- Bump to 0.1.2 and publish to PyPI
-
-## 2026-03-06 (feature)
-
-- `--version` / `-V` flag nel CLI (`fauxdata --version` → `fauxdata 0.1.1`)
-- Coverage threshold 80% in pytest config (`--cov-fail-under=80`); attuale: 83.76%
-- Nuovo campo `pattern` in ColumnSchema: genera stringhe che matchano un regex via pointblank
-- Nuovo campo `null_probability` in ColumnSchema: controllo granulare dei null (0.0–1.0), con validazione in parsing
-- Rimossa dipendenza `faker` (non usata, pointblank gestisce tutto)
-- Fix generator: `null_probability=None` non passato a pointblank (causa TypeError)
-- Test aggiornati: 79/79 pass
-
-## 2026-03-06 (tests)
-
-- Add pytest test suite: 65 tests, 100% pass, 0.44s
-- `tests/test_schema.py`: unit tests for YAML schema parsing (valid/invalid cases)
-- `tests/test_output.py`: unit tests for export functions (all formats, stdout, errors)
-- `tests/test_generator.py`: integration tests for generation (types, seed, unique, presets)
-- `tests/test_validator.py`: integration tests for validation rules (pass/fail scenarios)
-- `tests/test_cli.py`: CLI smoke tests via `typer.testing.CliRunner`
-- Add `[dependency-groups] dev` in `pyproject.toml` (pytest, pytest-cov); config via `[tool.pytest.ini_options]`
-
-## 2026-03-06
-
-- Initial implementation of `fauxdata` CLI
-- Stack: pointblank 0.22 (native generation + validation), polars, typer, rich, pyfiglet, questionary
-- Commands: `init`, `generate`, `validate`, `preview`
-- Example schemas: `people.yml`, `orders.yml`, `events.yml`
-- All schemas generate and validate cleanly (all rules PASS)
-- `locale` field at schema level maps to pointblank `country=` param

fauxdata_cli-0.2.0/RELEASING.md

@@ -1,83 +0,0 @@
-# Releasing
-
-Procedura per pubblicare una nuova release di `fauxdata` su PyPI.
-Il deploy **non è automatico**: nessun workflow GitHub Actions. Ogni step è manuale.
-
-## Versioning
-
-`MAJOR.MINOR.PATCH` (SemVer).
-
-- **subrelease / patch** (`0.1.5` → `0.1.6`): bugfix, nessuna modifica di API.
-- **minor** (`0.1.x` → `0.2.0`): nuove feature retrocompatibili.
-- **major** (`0.x` → `1.0.0`): breaking change.
-
-## Step
-
-1. **Aggiorna la versione** nei due file (devono restare allineati):
-   - `pyproject.toml` → `version = "X.Y.Z"`
-   - `src/fauxdata/__init__.py` → `__version__ = "X.Y.Z"`
-
-2. **Aggiorna `LOG.md`**: nuova sezione in cima con data `YYYY-MM-DD` e le modifiche.
-
-3. **Test**: devono passare tutti.
-
-   ```bash
-   uv run pytest tests/ -q
-   uv run fauxdata --version   # deve stampare la nuova versione
-   ```
-
-4. **Build**:
-
-   ```bash
-   rm -rf dist/
-   uv build
-   ls dist/   # fauxdata_cli-X.Y.Z-py3-none-any.whl + .tar.gz
-   ```
-
-5. **Aggiorna la CLI installata localmente** (`fauxdata` è installato come `uv tool`):
-
-   ```bash
-   uv tool install --reinstall .   # reinstalla dalla working copy
-   fauxdata --version              # deve stampare la nuova versione
-   ```
-
-6. **Commit + tag + push**:
-
-   ```bash
-   git add pyproject.toml src/fauxdata/__init__.py LOG.md
-   git commit -m "chore: vX.Y.Z — <sintesi>"
-   git tag -a vX.Y.Z -m "vX.Y.Z — <sintesi>"
-   git push origin main
-   git push origin vX.Y.Z
-   ```
-
-7. **Pubblica su PyPI** (richiede token PyPI — step da eseguire a mano):
-
-   ```bash
-   uv publish              # oppure: twine upload dist/*
-   ```
-
-   Il token si passa via `UV_PUBLISH_TOKEN` o `--token`. Non committare mai il token.
-
-8. **Verifica / aggiorna da PyPI** (il pacchetto su PyPI è `fauxdata-cli`):
-
-   ```bash
-   uvx fauxdata@X.Y.Z --version          # verifica al volo la versione pubblicata
-
-   pip install --upgrade fauxdata-cli     # aggiorna un'installazione pip esistente
-   # oppure, se installato come uv tool:
-   uv tool upgrade fauxdata-cli
-   ```
-
-9. **GitHub Release**: dal tag già pushato (il tag da solo **non** crea la release).
-   **Titolo e note devono essere in inglese.**
-
-   ```bash
-   gh release create vX.Y.Z --title "vX.Y.Z" --notes "<changelog in English>"
-   ```
-
-## Note
-
-- Se una release chiude una issue, referenziarla nel commit/tag (`#N`) e chiudere la issue con un commento che linka al commit.
-- La versione è testata dinamicamente (`test_cli_version` legge `__version__`), quindi il bump non rompe i test.
-- **Tag ≠ GitHub Release**: `git push origin vX.Y.Z` crea solo il tag; la pagina di release va creata a parte con `gh release create` (step 9).

fauxdata_cli-0.2.0/docs/deployment.md

@@ -1,90 +0,0 @@
-# Deployment rules
-
-## Pre-release checklist (always)
-
-1. Run tests locally — must all pass:
-
-```bash
-uv run pytest
-```
-
-Coverage must stay above 80%. If it drops, fix before proceeding.
-
-2. Bump version in **both**:
-   - `src/fauxdata/__init__.py` → `__version__ = "X.Y.Z"`
-   - `pyproject.toml` → `version = "X.Y.Z"`
-
-3. Update `LOG.md` with a summary of changes under a new date heading.
-
----
-
-## GitHub release (tag + release notes)
-
-```bash
-# Create and push annotated tag
-git tag -a vX.Y.Z -m "vX.Y.Z"
-git push origin vX.Y.Z
-```
-
-Then create a GitHub release via `gh`:
-
-```bash
-gh release create vX.Y.Z \
-  --title "vX.Y.Z" \
-  --notes "$(cat <<'EOF'
-## What's new
-
-- Short bullet list of user-facing changes
-- Include new fields, commands, bug fixes
-
-## Breaking changes
-
-- List any breaking changes here (or remove section if none)
-
-## Installation
-
-\`\`\`bash
-pip install fauxdata-cli==X.Y.Z
-\`\`\`
-
-Full changelog: https://github.com/aborruso/fauxdata/commits/vX.Y.Z
-EOF
-)"
-```
-
-Release notes style: **concise, nerd-friendly, technical**. List the actual changes with enough detail that a developer understands what changed and why.
-
----
-
-## PyPI publish (via twine)
-
-```bash
-# Build
-uv build
-
-# Check the dist
-twine check dist/*
-
-# Publish
-twine upload dist/*
-```
-
-Requires `~/.pypirc` configured with PyPI token, or set `TWINE_USERNAME`/`TWINE_PASSWORD` env vars.
-
----
-
-## Order of operations
-
-```
-uv run pytest          # must pass 100%
-bump version           # __init__.py + pyproject.toml
-update LOG.md
-git commit + git push
-git tag + git push tag
-gh release create      # with release notes
-uv build
-twine check dist/*
-twine upload dist/*
-```
-
-Never publish to PyPI without a corresponding GitHub release.

fauxdata_cli-0.2.0/docs/future-ideas.md

@@ -1,8 +0,0 @@
-# Future ideas
-
-Ideas from the pointblank 0.26-1.0.1 releases, not yet planned (2026-10-11).
-
-- Related tables: generate linked datasets (e.g. people and orders) and check foreign keys with `col_vals_in_table()` (pointblank 0.27).
-- Coded missing values: a schema field for sentinel values like `-99` or `N/A`, generated and validated via `MissingSpec` and `col_pct_missing()` (pointblank 0.26).
-- Schema export: let `infer` also write JSON Schema, Frictionless, dbt or ODCS via `export_contract()` (pointblank 0.26/0.27).
-- Fidelity report: compare the real dataset with the synthetic one using `DataScan.compare()` (PSI, Kolmogorov-Smirnov) to show how close the shapes are (pointblank 0.27).