Skip to main content

Hugpy settings

The shared settings layer extracted from Hugpy Wrapper's terminal harness. Wrapper and Hugpy Harness use this package directly instead of maintaining duplicate implementations. It uses only the Python standard library and has no dependency on either application, model engines, or a database driver.

The layer owns settings snapshots and redaction, field schemas, inheritance reports, editing controls, terminal navigation, and the remote folder picker. The running Wrapper remains responsible for validation, persistence, resource admission, and applying changes through its existing HTTP API.

from hugpy_settings.settings_view import show_settings, run_settings, snapshot

# gateway exposes api_key and models(); the host supplies endpoint discovery.
show_settings(gateway, base, model=model_key, as_json=True)
# A curses host can embed the same editor:
run_settings(screen, gateway, base, model=model_key, drain=drain, wait=wait)

drain is an optional event-draining callback. wait(title, operation) is an optional host callback for displaying progress around blocking work. Hosts own the terminal lifecycle. JSON and text reports remain available without curses.

Implementation modules:

  • settings_view: snapshots, reports, and terminal entry points.
  • settings_schema: model and box field descriptions.
  • settings_controls: parsing, HTTP updates, and editing workflows.
  • settings_widgets: dropdowns, mouse handling, and remote directory browsing.

Wrapper's fitevict.cli.settings_* and Harness's hugpy_harness.tui.views.settings_* paths alias these same modules, preserving existing callers and shared module state. New callers should import hugpy_settings modules directly. Wrapper's schema was used as the source of record; Harness's stale video_allow_cpu UI entry was not carried forward.

For source development, install this package into each host's development environment before installing that host:

python3 -m pip install -e /path/to/staging/hugpy-settings/package

Both Debian builders build and bundle the shared wheel alongside their own wheel. HUGPY_SETTINGS_SOURCE can override the sibling source directory. The package must be published to the chosen Python index before distributing Wrapper or Harness wheels that depend on hugpy-settings==0.1.2 through it.

Fleet terminal compatibility release — 2026-10-22

Composites dropdowns and sliders into the native input window so the background terminal cannot repaint over dense menus.

Metadata

Release files for hugpy-settings 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hugpy-settings 0.1.3
File Size Uploaded Provenance
hugpy_settings-0.1.3.tar.gz 29.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for hugpy-settings 0.1.3
File Interpreter ABI Platform
hugpy_settings-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 60.6 kB

Release files / hugpy_settings-0.1.3.tar.gz

Download URL hugpy_settings-0.1.3.tar.gz
Size 29.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5161fbfa09ab854240a8a6f2999039842617e962d096ae6e6bafc7f80a13fb0a
BLAKE2b-256 checksum
How to use checksums
ee1a253fe2cd8dbe8b45884f42a89a73742e6b82578fb45f41ec0e164cc91d3a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / hugpy_settings-0.1.3-py3-none-any.whl

Download URL hugpy_settings-0.1.3-py3-none-any.whl
Size 31.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
54159c446243283b257b6f9beade5275923967d1d3cd753a35d6fc1df2820309
BLAKE2b-256 checksum
How to use checksums
91fd98c2850f46256ad98e3ddbd584bb6e649c2b16c9377dd55da180f8347554
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for hugpy-settings 0.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page