This release is a pre-release and may not be stable for production use.
inxs – XML transformations without boilerplate.
inxs is inexcessive.
inxs is not XSLT.
inxs is ISC-licensed.
inxs is fully documented here: https://inxs.readthedocs.io.
At a glimpse
inxs |
XSLT |
|---|---|
|
|
inxs |
XSLT |
|---|---|
|
|
Here you can find the source repository and issue tracker of inxs.
Roadmap
0.1b0
enough documentation to get someone started
take it to the cheeseshop
0.1
reasonable test coverage
some usages in the wild / feedback thereof
History
0.1a (unreleased)
First release on PyPI.
Metadata
Release files for inxs 0.1a0
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 |
|---|---|---|---|---|
| inxs-0.1a0.tar.gz | 19.5 kB | Without provenance | Details for inxs-0.1a0.tar.gz |
Release files / inxs-0.1a0.tar.gz
| Download URL | inxs-0.1a0.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d79bb0c26443fd714cd4cd0097fa366ddde10ae999ed55e67b7ab4dd80200c6
|
|
BLAKE2b-256 checksum How to use checksums |
44a8e58a790efa3ff37c8a7f52ef97d6c8d1cbeecb231a7e8ec305964bdd7dd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for inxs 0.1a0
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.