python-json-patch
Applying JSON Patches in Python
Library to apply JSON Patches according to RFC 6902
See source code for examples
- Website: https://github.com/stefankoegl/python-json-patch
- Repository: https://github.com/stefankoegl/python-json-patch.git
- Documentation: https://python-json-patch.readthedocs.org/
- PyPI: https://pypi.org/project/jsonpatch/
- CI: https://github.com/stefankoegl/python-json-patch/actions
- Coveralls: https://coveralls.io/github/stefankoegl/python-json-patch
Running external tests
To run external tests (such as those from https://github.com/json-patch/json-patch-tests) use ext_tests.py
./ext_tests.py ../json-patch-tests/tests.json
Running property-based tests
Property-based tests using Hypothesis are in property_tests.py. Properties that the implementation does not satisfy yet are marked as expected failures.
pip install hypothesis
python property_tests.py
Set HYPOTHESIS_PROFILE=thorough to run many more examples.
1 maintainer
Metadata
1 maintainer
Release files for jsonpatch 1.36
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 |
|---|---|---|---|---|
| jsonpatch-1.36.tar.gz | 40.0 kB | With provenance | Details for jsonpatch-1.36.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jsonpatch-1.36-py3-none-any.whl | Python 3 | none | any | Details for jsonpatch-1.36-py3-none-any.whl |
Total release size: 57.1 kB
Release files / jsonpatch-1.36.tar.gz
| Download URL | jsonpatch-1.36.tar.gz |
|---|---|
| Size | 40.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e110cb3c5a1c8768f7170bf8fb9887c4aa575fba74c95239e868b494bd9a522
|
|
BLAKE2b-256 checksum How to use checksums |
8e39c534bb172e9318400d5631074b1eda6c78b7c918d0f04233b50caa8e2c10
|
| 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 Oct 19, 2026.
Transparency logRelease files / jsonpatch-1.36-py3-none-any.whl
| Download URL | jsonpatch-1.36-py3-none-any.whl |
|---|---|
| Size | 17.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa3ffbc15816644ffcc6b13712dacbc99f6f6dde302abc66983f9831d35630a5
|
|
BLAKE2b-256 checksum How to use checksums |
d9c0f2b34ce5fa98bde1bab4ff25f48064d09a078c40f4f53f65276a812d5e8a
|
| 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 Oct 19, 2026.
Transparency logSecurity for jsonpatch 1.36
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 jsonpatch-1.36.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 19, 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.
