opendxp is now noulxp
OpenDXP was renamed NoulXP in version 0.4.0. Nothing else changed: the format, the answers and the protocol are the same.
pip install noulxp
noulxp serve ./my-package
This package only installs noulxp and keeps the old names working:
import opendxp (and every opendxp.* module) is noulxp, and the opendxp
command runs noulxp. Packages made with opendxp (odxp.json, odxp/0.x)
run on noulxp as they are.
Code, specification and changelog: https://github.com/systemonemodels/noulxp
Metadata
Release files for opendxp 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 | |
|---|---|---|---|
| opendxp-0.4.0.tar.gz | 2.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opendxp-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 kB
Release files / opendxp-0.4.0.tar.gz
| Download URL | opendxp-0.4.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71c065467ae77b6af2e19f380676202b406355b5d284f97667529446d8fcb827
|
|
BLAKE2b-256 checksum How to use checksums |
70b5c67294afa6240f29d4e93350070ca1805c21db52dd10966ac0b506692984
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / opendxp-0.4.0-py3-none-any.whl
| Download URL | opendxp-0.4.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
740360c7c39f7e84fbd38db07b330772bbf93f3b37a254dfe94877a592617f50
|
|
BLAKE2b-256 checksum How to use checksums |
a04a35eeea2e755ee30421032518efd98f89dde4508d1b8026bfcefba3c8e7b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency log