This is a not-very-serious attempt at a command-line XML viewer that does pretty-printing, syntax highlighting, and someday maybe node folding.
I started this to learn more about curses, so I’m duplicating a lot of stuff you could otherwise accomplish by piping xmllint into less.
One major caveat is that performance will degrade the further down you scroll in a large file.
1 maintainer
Metadata
1 maintainer
Release files for cursexml 0.1.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 | |
|---|---|---|---|---|
| cursexml-0.1.0.tar.gz | 3.1 kB | Without provenance | Details |
Release files / cursexml-0.1.0.tar.gz
| Download URL | cursexml-0.1.0.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
199598b76375e5fe0027dd10989f5f2e6bd4cdf041c57a0208719191b6d72531
|
|
BLAKE2b-256 checksum How to use checksums |
a8fd24e03e93785145b2f8cda2f5833493a7d2016be531e872476dd497568af0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cursexml 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.
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.
