hexy-py
Python bindings for the hexy-core Rust crate. python/hexy/__init__.pyi documents
every class and method.
HexFileholds an image as segments and has a method for every core operation, named as thePipelinestage it configures:fill,cut,merge,filter,align,checksum,process_data,verify,validation_structureand so on. Operations change the image in place;copy()andnormalized()return new ones.Pipelineruns the configured stages in HexView's order, whatever order they were set in, andapplyreturns aPipelineResultwith the image, the checksums, the data processing output and the validation structures.DataProcessing.sign,.mac,.xor,.encrypt,.decrypt,.compressand.decompressbuild the/DPoperations thatprocess_dataruns.from_fileandfrom_file_bytesdetect Intel HEX, S-Record or raw binary as the CLI does;from_intel_hex,from_srecand the others read a known format.to_*methods return file contents andwrite_*methods write them.
Conventions:
- A range is an
AddressRangeor range text as HexView reads it (0x1000-0x10FFor0x1000,0x100); methods that take several ranges take a list. - Checksum methods are HexView
/CSindices. Other selectors are lower-case names, such as"preserve","rsa-pss-sha256"or"overwrite-end". - Asymmetric keys are a key file's content (bytes) or key text (str). Symmetric keys
are the raw key (bytes) or key text (str), read as HexView reads a key file; see
docs/data-processing.mdfor the key formats. - Errors from the data are
hexy.HexyErrorsubclasses:RangeError,ParseError,OperationError,ProcessingErrorand itsVerificationError. Unknown selector names raiseValueError, and file errorsOSError.
Sparse files stay sparse. to_binary(fill_gaps=...) and fill_gaps() allocate across
the covered address span, so far-apart segments can produce large byte strings.
Metadata
Release files for hexy-py 0.4.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 | Actions |
|---|---|---|---|---|
| hexy_py-0.4.0.tar.gz | 134.5 kB | With provenance | Details for hexy_py-0.4.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| hexy_py-0.4.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for hexy_py-0.4.0-cp310-abi3-win_amd64.whl |
| hexy_py-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details for hexy_py-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
| hexy_py-0.4.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for hexy_py-0.4.0-cp310-abi3-macosx_11_0_arm64.whl |
| hexy_py-0.4.0-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details for hexy_py-0.4.0-cp310-abi3-macosx_10_12_x86_64.whl |
Total release size: 3.7 MB
Release files / hexy_py-0.4.0.tar.gz
| Download URL | hexy_py-0.4.0.tar.gz |
|---|---|
| Size | 134.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f174efd37df701dc43ea2dbcacc48e19938605257eab09f2fa9d2b3f6c521263
|
|
BLAKE2b-256 checksum How to use checksums |
c82f90eefd85b23d81093adcb3fda6ad9ed659c9847f0953a57c12099f97aacd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Nov 9, 2026.
Transparency logRelease files / hexy_py-0.4.0-cp310-abi3-win_amd64.whl
| Download URL | hexy_py-0.4.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 780.9 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7ed37844ef16ab69c8d0e767eff880fb593d5e7e974e7b620fe4fb8885abbbcc
|
|
BLAKE2b-256 checksum How to use checksums |
c7db1b01481fe1f6e09e3120f8f0c67302de355995edc4d8c08254e8e46daf5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Nov 9, 2026.
Transparency logRelease files / hexy_py-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | hexy_py-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 988.5 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
3bb841a6e63658c53d158a5a4adefd06a2dde0688aa551df5003512ba723553d
|
|
BLAKE2b-256 checksum How to use checksums |
7854075e665ec878a34bf216df67b22ad7aff7648f3ee9644758258985d2232e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Nov 9, 2026.
Transparency logRelease files / hexy_py-0.4.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | hexy_py-0.4.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 874.0 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
aebabd02209e9e5e905a2370ddbface7f99c2b1c95e8bd04bb7dcc4378402a36
|
|
BLAKE2b-256 checksum How to use checksums |
38d06205286ae502996ef222f3fc0955dab131c13fc1e2af90e2eb6c76ab77c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Nov 9, 2026.
Transparency logRelease files / hexy_py-0.4.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | hexy_py-0.4.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 937.5 kB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
1c59c20d5b7b4c170ed01ae01db2fbcba3d46157ff96a54bec74e05a26fb8cb7
|
|
BLAKE2b-256 checksum How to use checksums |
9b39615a6f9c2105c42b3a38a6a9f8cc81b0a39de9f2b9746e48e6085435fca2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Nov 9, 2026.
Transparency logSecurity for hexy-py 0.4.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.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for hexy_py-0.4.0.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 Nov 9, 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.