json interactive stream editor
A tool inspired by Ultimate Plumber that uses jq to process JSON and show you the results instantly, to enable greater interactivity.
A manual for jq can be found here.
Download & Install
sudo apt install jq # <-- Install the jq tool, on MacOS install using `brew install jq`
pip3 install jqed
Usage / Examples
cat some_file.json | jqed
ip --json link | jqed
Metadata
Release files for jqed 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jqed-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for jqed-0.1.4-py3-none-any.whl |
Release files / jqed-0.1.4-py3-none-any.whl
| Download URL | jqed-0.1.4-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e5e5e33108d756890a3b644d7f1e2cdc21082e40293e3c68ec8c467eeafea95
|
|
BLAKE2b-256 checksum How to use checksums |
d6297ae8971ef17b7acbe30324999831868d8f7ae4733e35cba9a7441a7b0ad7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.5
|
Security for jqed 0.1.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.