PHX (Passive House Exchange):
The Passive House Exchange (PHX) package enables users to move building model data into and out of the Passive House energy modeling software platforms (PHPP or WUFI-Passive).
PHX converts live Honeybee models carrying honeybee-ph data into 'PH-Style' objects and then manages data input to proprietary PH calculators such as PHPP and WUFI-Passive. File-oriented workflows may first read a HBJSON file into that Honeybee model.
PHX itself does not have serialization / deserialization, and is not intended to be stored or written directly: it is an in-memory-only model which is created as a middle-step when moving the building data from the source (usually a HBJSON file) to the destination (PHPP, WUFI-Passive).
This library is designed to be used as part of the Honeybee-PH plugin workflow, or other similar tools which require interfacing with the Passive House modeling platforms.
from PHX.conversion import from_honeybee
phx_project = from_honeybee(hb_model)
Packages:
-
conversion: Public live Honeybee / honeybee-ph
Model→ transientPhxProjectAPI. -
from_HBJSON: Honeybee conversion implementation and HBJSON file-reading helpers retained for existing workflows.
-
from_WUFI_XML: Modules used to create a new PHX model from an existing WUFI-Passive XML file.
-
from_PHPP: Modules used to create a new PHX model from an existing PHPP file.'
-
model: The PHX model classes and structures. These objects are designed to be built by one of the 'from_*' libraries above.
-
to_PHPP: Libraries to allow for the export of PHX data to a PHPP Microsoft Excel spreadsheet.
-
to_WUFI_XML: Libraries to allow for the export of a WUFI-Passive XML file with all of the PHX model data. This XML file can then be opened from within the WUFI-Passive application.
-
to_PPP / to_METr_JSON: Additional exporters for the PPP and METr-JSON target formats.
Development:
- Python: 3.10+ (CPython). Runs as a library/CLI, not inside Rhino (except the
PHX/run.pyGrasshopper shim). - Tests:
python -m pytest tests/. - Commits: conventional commits (
feat(scope):/fix(scope):) drive semantic-release auto-publishing to PyPI. - Agent/contributor orientation:
CLAUDE.md, thecontext/folder, and the deep architecture docs underdocs/dev/anddocs/reference/.
More Information:
For more information on the use of these tools, check out the the Passive House Tools website: https://passivehousetools.com/
1 maintainer
Metadata
1 maintainer
Release files for PHX 1.57.7
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 | |
|---|---|---|---|---|
| phx-1.57.7.tar.gz | 388.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phx-1.57.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 859.4 kB
Release files / phx-1.57.7.tar.gz
| Download URL | phx-1.57.7.tar.gz |
|---|---|
| Size | 388.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf07fed059e2e74c7e2e1214728f449e25a81c16e2b8c0e618ca2dc1f998630f
|
|
BLAKE2b-256 checksum How to use checksums |
c137f92f1092606d3dc6a6d74e7b3d5f0ac04b9e35ddfb74b31c59651141c45e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / phx-1.57.7-py3-none-any.whl
| Download URL | phx-1.57.7-py3-none-any.whl |
|---|---|
| Size | 470.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eece04805415224b6f52ead13c41af8437be55d10666d59158e4011ea7ba3bcd
|
|
BLAKE2b-256 checksum How to use checksums |
c3e69dba30a0684bcb405664a56003c7a0f69144cc2704cc29ff27c47c6bd9b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for PHX 1.57.7
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for phx-1.57.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA 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.
