User#
PyUnitWizard appears in two very different contexts, and each context needs a clear reading path.
Some readers are maintainers evaluating whether to integrate PyUnitWizard in a scientific library. Others are scientists using a library that already embeds PyUnitWizard and just want reliable, predictable behavior in their scripts.
This section is written for both profiles. Pick the route that matches your role first, then skim the other route so you understand the full contract between library maintainers and library users.
Route A: Library Integrators#
Go to Library Integrators.
In this route you will learn how to:
configure PyUnitWizard once and keep runtime deterministic,
normalize and validate quantities at API boundaries,
standardize outputs so downstream tools receive consistent units.
Route B: End Users of Integrating Libraries#
Go to End Users.
In this route you will learn how to:
reason about quantity parsing, conversion, and compatibility in day-to-day scripts,
diagnose common failures quickly,
communicate reproducible unit issues to library maintainers.
Both routes converge on the same objective: unit-safe workflows across scientific Python libraries without hidden assumptions.
Public API Map#
When you need complete function-level reference:
Notebook Route#
If you prefer notebook-first learning, follow this practical sequence:
Notebook note:
The Markdown route (
library-integrators.md,end-users.md, and linked guides) is the maintained canonical route for RC/stable behavior.Notebooks are kept for hands-on exploration and may include historical narrative fragments.