A TiddlyWeb plugin which adds a _hash field to outgoing tiddlers.
When a tiddler is get from the store, if there is no _hash, then the hash is added to the outgoing tiddler. It is _not_ saved
This is done to allow quick comparisons between tiddlers which may have different names but may have the same set of content characteristics.
The hash_tiddler method is exposed so that stores can create a hash prior to a put to the store. See tiddlywebplugis.tiddlyspace.store for an example.
To use add ‘tiddlywebplugins.hashmaker’ to system_plugins and twanager_plugins in tiddlywebconfig.py. Optionally define hashmaker.attributes to be a list of strings representing the attributes or fields of a tiddler which are to be hashed. The default is:
[‘text’]
Metadata
Release files for tiddlywebplugins.hashmaker 0.9
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 | |
|---|---|---|---|---|
| tiddlywebplugins.hashmaker-0.9.tar.gz | 6.3 kB | Without provenance | Details |
Release files / tiddlywebplugins.hashmaker-0.9.tar.gz
| Download URL | tiddlywebplugins.hashmaker-0.9.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73059f57795615cb9d4522c91ef8ac5b1e26679d68cad144953ad69d77ab72b1
|
|
BLAKE2b-256 checksum How to use checksums |
8d3a474d7aa3a4356a22fc2289824ee8cccc85cd05117001d2921f688500cda1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tiddlywebplugins.hashmaker 0.9
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.