GinGin is a hybrid of WIKI and BLOG. Users of GinGin can setup tags for their documents. The documents will be hyper-linked, automatically, when tags are in the content of them. In another word, GinGin will create cross-reference for documents by the tags specified by users.
GinGin also has capability to tag URLs. URLs are associated with tags and cross-referenced for documents.
1 maintainer
Metadata
1 maintainer
Release files for GinGin 1.0.1
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 | |
|---|---|---|---|---|
| GinGin-1.0.1.tar.gz | 62.8 kB | Without provenance | Details |
Release files / GinGin-1.0.1.tar.gz
| Download URL | GinGin-1.0.1.tar.gz |
|---|---|
| Size | 62.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8da8fe0aee9d91248fa6fd0e5b7074ec91bc5b81ad1732a019c9fcb8a8da1a00
|
|
BLAKE2b-256 checksum How to use checksums |
f5e9f3f4e0e58bdd3047f860f5d5dfa503532f53d1e5c0d40ee5fca104a61590
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for GinGin 1.0.1
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.
