This is an XMLRPC client for Wordpress blogs. It is command-line, rather than GUI, based and reads markdown formatted text files to post to a web log. The text files must also be formatted with a header, see the usage documentation for details.
In addition to support for posting, a number of blog related administrative actions are supported like commenting, comment editting and moderation, post deletion and so forth. See the documentation for a full description.
The source for blogtool lives here.
1 maintainer
Metadata
1 maintainer
Release files for blogtool 1.1.2
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 | |
|---|---|---|---|---|
| blogtool-1.1.2.tar.gz | 38.9 kB | Without provenance | Details |
Release files / blogtool-1.1.2.tar.gz
| Download URL | blogtool-1.1.2.tar.gz |
|---|---|
| Size | 38.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d272a988d59e6cbedc65c568ddbfdf58d5fca18a560790b108f55ad0f002c8a2
|
|
BLAKE2b-256 checksum How to use checksums |
a6bec379768c62da704a0eba4c1aaec59918918415053ad86d5b3d13e261834e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for blogtool 1.1.2
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.
