Hugpy
The complete Hugpy Python suite in one install. hugpy declares the component
dependencies and exposes their Python modules through lazy imports. Components
keep their own implementations, releases, and canonical import paths.
Install
Python 3.11 or newer is required. After publication:
python -m pip install hugpy
python -m pip install 'hugpy[providers]' # shared Serve, Claude, and GPT
python -m pip install 'hugpy[identity]' # Identity
python -m pip install 'hugpy[all]' # suite, providers, and Identity
The staged version is 0.3.0rc1. To select this candidate explicitly after it
is published, use python -m pip install 'hugpy==0.3.0rc1' (with extras if
needed). A normal install selects stable releases by default.
The default install includes every Hugpy Python component listed below and the
shared Toolserver package. Claude, GPT, Serve, and Identity are optional.
The earlier candidate's worker, media, video, and agent extras remain
accepted; those components are now included by default.
Backend extras remain on their owning packages, for example
hugpy-media[audio], hugpy-wrapper[transformers], or
abstract-identity[render]. The umbrella does not request every backend extra
or bundle model weights. Station and the native Llama server are installed
separately through their own distribution channels.
Imports
import hugpy
from hugpy import core, engine, wrapper, harness, fleet
from hugpy import media, video, oracle, storage, agent
from hugpy import settings, platform, tools, toolserver, terminal
# Convenience exports from hugpy_engine:
from hugpy import execute_prompt, execute_prompt_stream, execute_chat_stream
# With the matching optional extras installed:
from hugpy import serve, claude, gpt, identity
import hugpy loads no component. Accessing an alias imports and caches that
component's actual module; for example, hugpy.wrapper is fitevict and
hugpy.media is hugpy_media. Component initialization happens when that
component is requested. Optional components are listed by dir(hugpy) but
excluded from star imports.
| Alias | Canonical Python module | Distribution | Install |
|---|---|---|---|
settings |
hugpy_settings |
hugpy-settings |
Default |
platform |
hugpy_platform |
hugpy-platform |
Default |
tools |
hugpy_tools |
hugpy-tools |
Default |
toolserver |
abstract_toolserver |
abstract-toolserver |
Default |
storage |
hugpy_storage |
hugpy-storage |
Default |
engine |
hugpy_engine |
hugpy-engine |
Default |
wrapper |
fitevict |
hugpy-wrapper |
Default |
core |
hugpy_core |
hugpy-core |
Default |
terminal |
hugpy_terminal |
hugpy-terminal |
Default |
harness |
hugpy_harness |
hugpy-harness |
Default |
fleet |
hugpy_fleet |
hugpy-fleet |
Default |
agent |
hugpy_agent |
hugpy-agent |
Default |
media |
hugpy_media |
hugpy-media |
Default |
oracle |
hugpy_oracle |
hugpy-oracle |
Default |
video |
hugpy_video |
hugpy-video |
Default |
serve |
abstract_serve_core |
abstract-serve-core |
hugpy[providers] |
claude |
abstract_claude |
abstract-claude |
hugpy[claude] or hugpy[providers] |
gpt |
abstract_gpt |
abstract-gpt |
hugpy[gpt] or hugpy[providers] |
identity |
abstract_identity |
abstract-identity |
hugpy[identity] |
For submodules, use canonical paths, for example import hugpy_media.extract.
The aliases support attribute access and from hugpy import ...; they do not
create a second submodule tree under hugpy. The three inference functions
above are forwarded unchanged from hugpy_engine.
This package installs no hugpy or hpy command. Each component owns its own
command line and runtime configuration.
Release preparation
Build the source distribution and wheel from this directory:
python -m build
Dependency minimums describe the intended component release set. Publish the components before the umbrella, then resolve and install the built wheel in a clean Python 3.11+ environment. The minimum versions match the staged component metadata at preparation time; update them if the component releases change the required baseline. Public dependency resolution and runtime installation remain release checks once those component uploads are available.
The wheel and source distribution contain the umbrella source, metadata, and license. Building this candidate does not publish it or install the suite.
1 maintainer
Metadata
1 maintainer
Release files for hugpy 0.3.0
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 | |
|---|---|---|---|---|
| hugpy-0.3.0.tar.gz | 5.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hugpy-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.5 kB
Release files / hugpy-0.3.0.tar.gz
| Download URL | hugpy-0.3.0.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16410acaf64b6f51faebde4e05c7f1677fb183f901a1a2114542dd45e3755a93
|
|
BLAKE2b-256 checksum How to use checksums |
74036764b7b29b0f9a4f55d43e1c84487d19acc194f8c720cd2f4046c0182ca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / hugpy-0.3.0-py3-none-any.whl
| Download URL | hugpy-0.3.0-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6356075d38d8ffcf2ff8ae29899ad8319e79abcd03fced253f153fb807e135ef
|
|
BLAKE2b-256 checksum How to use checksums |
4eac31bbcefcfcaa95ad80cf8fc8ed5101985d1245fd766e8c0b47d054b529d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for hugpy 0.3.0
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.
