tiddlywebplugins.plugins is a system_plugin for TiddlyWeb which will read a file in the current instance as a list of additional system_plugins to add to the instance.
This is done so automation of the plugins currently in use in an instance is more flexible.
To use, add ‘tiddlywebplugins.plugins’ to system_plugins in tiddlywebconfig.py. Add other system_plugins to a file named ‘extra_plugins’. This file can be overridden by setting ‘plugin_file’ in tiddlywebconfig.py.
Copyright 2009 Chris Dent <cdent@peermore.com>, who was assuming someone else was going to write this in their own efforts to better manage configurations.
Licensed under the same terms as TiddlyWeb itself.
For more on TiddlyWeb see http://tiddlyweb.com/
Metadata
Release files for tiddlywebplugins.plugins 0.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 | Actions |
|---|---|---|---|---|
| tiddlywebplugins.plugins-0.2.tar.gz | 2.1 kB | Without provenance | Details for tiddlywebplugins.plugins-0.2.tar.gz |
Release files / tiddlywebplugins.plugins-0.2.tar.gz
| Download URL | tiddlywebplugins.plugins-0.2.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb7b6c46aa78d166f220d4a205b31a58ddd78455f66ee319ce600b0cc1ba3cae
|
|
BLAKE2b-256 checksum How to use checksums |
b086f1555a81a88793979fa3bf40d942ce33c0c33eceabe7d89110274fa429fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tiddlywebplugins.plugins 0.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.