jpx
Python bindings for jpx, a JMESPath query engine with 460+ extended functions on top of the standard JMESPath specification.
The bindings are built in Rust with PyO3 and ship as abi3 wheels, so a single wheel per platform works on CPython 3.9 and newer.
Install
pip install jpx
Quick start
import jpx
data = {"people": [{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]}
# Run a query
jpx.search("people[?age > `28`].name", data)
# ['Alice']
# Compile once, reuse many times
expr = jpx.compile("people[*].name")
expr.search(data)
# ['Alice', 'Bob']
# Validate an expression without running it
jpx.validate("people[*].name")
# {'valid': True, ...}
Discovering functions
jpx.list_categories() # extension categories
jpx.list_functions("string") # functions in a category
jpx.describe("group_by") # metadata for a single function
Full engine
JpxEngine exposes the complete engine: batch evaluation, function
introspection, JSON utilities (diff, patch, merge, stats, paths), and a
session-scoped named query store.
from jpx import JpxEngine
engine = JpxEngine()
engine.evaluate("a.b", {"a": {"b": 1}})
engine.diff({"a": 1}, {"a": 2}) # RFC 6902 patch
engine.stats({"a": [1, 2, 3]}) # structural stats
Links
- Documentation: https://joshrotenberg.github.io/jpx/
- Source and issues: https://github.com/joshrotenberg/jpx
License
MIT OR Apache-2.0
1 maintainer
Metadata
1 maintainer
Release files for jpx 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| jpx-0.1.0-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details for jpx-0.1.0-cp39-abi3-win_amd64.whl |
| jpx-0.1.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details for jpx-0.1.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| jpx-0.1.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details for jpx-0.1.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| jpx-0.1.0-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details for jpx-0.1.0-cp39-abi3-macosx_11_0_arm64.whl |
| jpx-0.1.0-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details for jpx-0.1.0-cp39-abi3-macosx_10_12_x86_64.whl |
Total release size: 14.1 MB
Release files / jpx-0.1.0-cp39-abi3-win_amd64.whl
| Download URL | jpx-0.1.0-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
1bc80cadff14c2f6008dc1e256c8c78f064668b9da9ac411279033d79de16efc
|
|
BLAKE2b-256 checksum How to use checksums |
29b942afbb660fdb4b279a6ff71d816f24b181f95a2055849419a9c871a6fa50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logRelease files / jpx-0.1.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | jpx-0.1.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
9c1a4561dbc8f6cfce7bd8b34da434322cdb1cb48f529bbf5881f482c3cd77a3
|
|
BLAKE2b-256 checksum How to use checksums |
e095a17c97a9eca8548c91c770f88ec2658df65200b845bda1bf2204bf9a48a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logRelease files / jpx-0.1.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | jpx-0.1.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 3.1 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e41e1f4a42d1df3469dbe9a9a69fe001dbfe081d88f7ec2dff59adee21d83973
|
|
BLAKE2b-256 checksum How to use checksums |
b40344347dabdb24ce19b19e12569cf4ea076070429a983a2fd81a6a1c7d4994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logRelease files / jpx-0.1.0-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | jpx-0.1.0-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
77fbc7681906bfc06931b1484d73bb79637308b0040c570034487e1103c16621
|
|
BLAKE2b-256 checksum How to use checksums |
b802ac0c5cc26b4c60fc0dee9375f1c44470147860752060024c95c4c89d5b3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logRelease files / jpx-0.1.0-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | jpx-0.1.0-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
c29d539431661fc73d0d007c5fac334c8ebaae44f6c651c57b1f4d2754adc5d2
|
|
BLAKE2b-256 checksum How to use checksums |
014d5c0e7730626a0a761e0c97ad38083db9d8187b99596d32d9079e2b53d59c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logSecurity for jpx 0.1.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 jpx-0.1.0-cp39-abi3-win_amd64.whl
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 Jun 10, 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.
