hank-format

Shared string formatting functions for standardizing names, dates, and times across the Hank AI stack.

pip install hank-format

Usage

from hank_format import as_name, as_date, as_date_str, as_datetime_str, as_time_str

as_name("Primary: John Doe")                       # 'DOE, JOHN'
as_name("Steven Hardman, APRN - CRNA")             # 'HARDMAN, STEVEN, APRN, CRNA'
as_date("12/31/2020 (age 30 yrs)")                 # datetime.date(2020, 12, 31)
as_date_str("01012024")                            # '2024-01-01'
as_datetime_str("2020-12-31T23:59")                # '2020-12-31 23:59:00'
as_datetime_str("23:59", precision="minute", default_date="2020-12-31")  # '2020-12-31 23:59'
as_time_str("11:30 pm")                            # '23:30'

API

Conventions:

• Inputs may be strings, date, datetime, time, or None. Other types raise TypeError.
• Object variants return None and string variants return "" when no usable value exists.
• Returned values are timezone-naive and have no microseconds. precision truncates, never rounds.
• Any parsed date more than two days in the future rolls back 100 years, including four-digit years and year-less MM/DD (12/31/45 is 1945; 12/26 without a time is 1926 when today is 2026-10-08). This is a two-digit-year heuristic inherited from pdf-extractor; strip or validate far-future dates before calling if you need them intact.
• Year-less MM/DD HH:MM strings take the current year, or the previous year if that would be in the future.

Migrating from pdf-extractor utils

Legacy as_time returned "" for anything without a time; the new datetime functions format a date-only value as midnight, hence the has_time guards.

Development

Requires uv.

uv sync                      # create .venv with Python 3.12 and the dev group
uv run pytest                # tests with 100% coverage enforced
uv run ruff check . && uv run ruff format --check .
uv run pyright
uv build                     # sdist + wheel into dist/

Releasing

1. Open a PR against main and add exactly one label: release:patch, release:minor, or release:major.
2. On merge, the Release workflow bumps __version__ in hank_format/__init__.py, runs the tests, builds, commits Release vX.Y.Z, tags it, and pushes. A separate publish job then uploads the built artifacts to PyPI.
3. If only the publish job fails (for example, trusted publishing is not configured yet), fix the cause and re-run that failed job. Do not re-run the whole workflow: the version is already bumped and tagged, so a full re-run would bump it again.

One-time setup:

• On pypi.org, under the hank-format project (or as a pending publisher), add a trusted publisher with owner hank-ai, repository hank-format, workflow release.yml, environment pypi.
• In the GitHub repo settings, create an environment named pypi.
• The workflow pushes the version-bump commit to main with the default GITHUB_TOKEN. If main is protected, allow the token to bypass the rule or supply a PAT in a RELEASE_TOKEN secret and use it in the checkout step.