hugpy-platform
The stdlib-first foundation that the hugpy arms build on: app directories, storage-root constants, executable resolution, a process-wide async runtime, hardware and process probes, and small formatting and result helpers.
Distribution hugpy-platform, import hugpy_platform.
Dependencies: abstract_essentials, platformdirs. Optional extra: hardware
(psutil).
Modules
import hugpy_platform re-exports only the light, side-effect-free accessors:
cache_dir,config_dir,data_dir,engine_dirhugpy_home,ensure_hugpy_home,hugpy_config_dir,hugpy_logs_dir,hugpy_run_dir,hugpy_state_dirmodels_rootEXE_SUFFIX,IS_LINUX,IS_MACOS,IS_WINDOWS,env_value
Import everything else by dotted path.
| module | what it provides |
|---|---|
app_dirs |
per-OS application directories, the single source of truth for them |
platform_facade |
OS facts and the env_value environment seam |
constants |
storage roots resolved from the environment: DEFAULT_ROOT, MODELS_HOME, UPLOADS_HOME, PROJECTS_HOME, IDENTITIES_HOME, …, HF_TOKEN, env_bool() |
utils |
small filesystem, message and naming helpers (get_messages, get_request_id, exists, …) |
async_runtime |
one long-lived event loop in a daemon thread: run, submit, await_sync, iter_sync |
binaries |
portable executable resolution: resolve_bin, with_exe |
module_imports |
lazy heavy imports with actionable errors: require, get_torch, get_transformers, get_whisper, … |
runner_config |
RunnerConfig, the common constructor state for media runner adapters |
results |
result-object adapters: result_text, vision_result_text, result_payload |
filesystem |
free_bytes, directory_bytes, is_within, write_text, … |
hardware |
total_vram_bytes (torch or nvidia-smi) |
procutil |
pid_alive, popen_detached, terminate_tree, reexec |
atomic_json, formatting, choices, verdict, versioning, client_liveness |
atomic JSON writes, byte formatting, value selection, VERDICT/SCORE/WHY parsing, version lookup, client-disconnect detection |
This package has no imports/ layer (see
the convention).
See also docs/packages.md and docs/architecture.md.
Metadata
Release files for hugpy-platform 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hugpy_platform-0.3.4.tar.gz | 43.9 kB | Without provenance | Details for hugpy_platform-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hugpy_platform-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for hugpy_platform-0.3.4-py3-none-any.whl |
Total release size: 102.3 kB
Release files / hugpy_platform-0.3.4.tar.gz
| Download URL | hugpy_platform-0.3.4.tar.gz |
|---|---|
| Size | 43.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17c711f977887386dce34005920fa1999adbbdf818e285d78c07f145d40719c1
|
|
BLAKE2b-256 checksum How to use checksums |
224a43b7e36f3d6e4241dde2656a6cd15409d223cbfa05a1b5899572954ec6fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / hugpy_platform-0.3.4-py3-none-any.whl
| Download URL | hugpy_platform-0.3.4-py3-none-any.whl |
|---|---|
| Size | 58.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af7005b2b00b0651efd1643ccdf9cd76f278f7dfb17d7a7e2695248d798ac81a
|
|
BLAKE2b-256 checksum How to use checksums |
2519c6a20179617dacc91af3cdfbce82ad3e276f138c8ae5fcb609a5e2deb2fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for hugpy-platform 0.3.4
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.