RFC Editor Tools Utility Code
This module contains a set of utility functions used by some of the RFC Editor tools. Long term, the goal is to incorperate these functions back into xml2rfc but having it separate allows for an easier modification of the functions as needed.
Changelog
Version 0.5.11 (Tue 1 Jan)
Add the info logging function for another output type
Add option to surpress populating default attributes from the DTD
Version 0.5.10 (XXX 2 Sept)
The no xinclude option is expanded to include processing <?rfc include=””?> PI
Version 0.5.6 (Mon 2 July)
Add option to not resolve entities for XML Linting
Fix problem with installing on a clean platform
Metadata
Release files for rfctools-common 0.5.11
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 |
|---|---|---|---|---|
| rfctools_common-0.5.11.tar.gz | 41.2 kB | Without provenance | Details for rfctools_common-0.5.11.tar.gz |
Release files / rfctools_common-0.5.11.tar.gz
| Download URL | rfctools_common-0.5.11.tar.gz |
|---|---|
| Size | 41.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67b739585dd6b8ebda015d6d819b0d7eb826bb201f76949f4d966fa6d6a87ec5
|
|
BLAKE2b-256 checksum How to use checksums |
6a952cd24c9c6b59cb7d25cfbc76ca55a673c18d380387f7c97dbb6fefaffc97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.9.1 pkginfo/1.4.1 requests/2.20.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.5 CPython/3.6.6
|
Security for rfctools-common 0.5.11
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.
