Skip to main content

hugpy-storage

STATUS: LIVE (2026-10-27). hugpy-core depends on this package and runs two of its modules as services: hugpy-core-downloader (python -m hugpy_storage.downloader.daemon) and hugpy-core-catalog (python -m hugpy_storage.hub.discovery). Core also registers the storage_bp and transfer_bp blueprints and uses transfer_api, model_paths and transfer.downloads (central model dirs, hub ids, staging-suffix rules). The 2026-10-15 note that called this package optional is superseded.

Distribution hugpy-storage, import hugpy_storage. Dependencies: abstract_essentials, huggingface_hub>=0.20, requests>=2.28, pydantic>=2, flask>=2. Extras: engine (hugpy-engine), test.

What it contains

This package manages model storage, metadata and transfers:

module role
downloader/ (daemon, queue, engine, presence) the model download queue and daemon
transfer/downloads.py ensure_model(key), download_one, ensure_models. On a worker (WORKER_CENTRAL_URL set) ensure_model resolves the model locally or from central and never reaches Hugging Face.
transfer/provision.py, transfer/sync.py resumable central and Hugging Face transfer and model sync
hub/ (api, token, metadata, options/) external provider transport, credentials, metadata, search and install options
models/ (physical, status_cache, presence) physical inventory and its caches
models/ (paths, marker, gguf, formats, config, preview, archive, admission) on-disk model layout, markers, inspection and lifecycle metadata
catalog/ (source, providers, events, bus) registry Protocol, injected hooks and catalog events
web/ (api, transfer) legacy Flask blueprints; hugpy.api: storage points to web.api:storage_bp
imports/ (constants, functions, classes, init_imports) Core-style shared vocabulary, pure helpers and common types
config/roots.py, platform/, schemas/, jobs/store.py environment-dependent roots, platform helpers, wire schemas and persistent jobs
commands/cli.py, console/, deploy/ command-line entry point, console helpers and service resources

Console scripts:

  • hugpy-storage (daemon, sync, status)
  • hugpy-downloader, an alias for the download daemon

No unit runs either on the live hosts.

docs/REGISTRY-DB-INDEX.md records the 2026-09-10 decision to keep hugpy.json markers as the per-model source of truth and to rebuild any aggregate index from them. The wrapper's marker store follows the same rule.

Package layout

The source follows Core's nested-package and shared-import convention:

hugpy_storage/
  imports/       constants.py, functions.py, classes.py, init_imports.py
  catalog/       source.py, providers.py, events.py, bus.py
  commands/      cli.py
  config/        roots.py
  console/       UI-facing adapters
  downloader/    daemon.py, engine.py, queue.py, presence.py
  hub/           api.py, token.py, metadata.py, options/
  jobs/          store.py
  models/        paths.py, marker.py, physical.py, admission.py, ...
  platform/      filesystem/process/environment helpers
  schemas/       models.py, install.py, download_schemas.py
  transfer/      downloads.py, provision.py, sync.py
  web/           api.py, transfer.py
  deploy/        packaged service resources

Internal imports and package entry points use these canonical paths. Existing flat paths and _lifted modules remain compatibility aliases to the same module objects, including private symbols and mutable state. For example, hugpy_storage.providers and hugpy_storage.catalog.providers share one set of injected hooks; importing the old name does not create another registry, metadata store, cache or bus. New integrations should use the nested paths. The executable compatibility paths python -m hugpy_storage.cli and python -m hugpy_storage.model_sync also delegate to the nested implementations.

imports.constants holds pure shared vocabulary; imports.functions holds environment parsing and timestamp helpers; imports.classes re-exports the lightweight catalog/provider contracts. imports.init_imports is the optional one-stop import surface. These modules do not initialize storage roots or clients. Environment-dependent roots retain their existing initialization in config.roots; importing it may create directories and seed cache environment variables, just as the old _lifted.constants did.

Metadata

Release files for hugpy-storage 0.2.19

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-storage 0.2.19
File Size Uploaded Provenance Actions
hugpy_storage-0.2.19.tar.gz 316.8 kB Without provenance Details for hugpy_storage-0.2.19.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hugpy-storage 0.2.19
File Interpreter ABI Platform Actions
hugpy_storage-0.2.19-py3-none-any.whl Python 3 none any Details for hugpy_storage-0.2.19-py3-none-any.whl

Total release size: 643.9 kB

Release files / hugpy_storage-0.2.19.tar.gz

Download URL hugpy_storage-0.2.19.tar.gz
Size 316.8 kB
Tags Source
SHA-256 checksum
How to use checksums
bf351af45360c8a24aa21deecf2b73cfb8a894315d68dd5610fe0eef846d24dc
BLAKE2b-256 checksum
How to use checksums
91f2a718d12c64c25627299c091390d5773b4ba40d32026205fc66ff674e7b9b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / hugpy_storage-0.2.19-py3-none-any.whl

Download URL hugpy_storage-0.2.19-py3-none-any.whl
Size 327.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3aa0b1b076343c060e8f07413d01c238aadae0654caafdb88b85f27f39fc66de
BLAKE2b-256 checksum
How to use checksums
ab7d8b4d01b6f88d0970b1a60241d4d7fc69f1327f360fd77624790e09d62b34
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for hugpy-storage 0.2.19

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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