A sphinx extension to replace the IndexEntries class.
Sphindexer = Sphinx + Indexer
THE GOAL
It’s to become the IndexEntries class.
It has the extention for kana_text.
FEATURE
Even when editing glossary with index_key, make clean is not necessary.
See/seealso appears at the first.
When there are multiple functions with the same name, the first one will not be left out.
It is relatively easy to customize the display order to your liking.
You must be able to develop sphinx extensions.
USAGE
conf.py
extensions = ['sphindexer']build ( without sphindexer ):
$ make htmlbuild ( with sphindexer ):
$ make idxr1 maintainer
Metadata
1 maintainer
Release files for sphindexer 0.12.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 |
|---|---|---|---|---|
| sphindexer-0.12.2.tar.gz | 19.4 kB | Without provenance | Details for sphindexer-0.12.2.tar.gz |
Release files / sphindexer-0.12.2.tar.gz
| Download URL | sphindexer-0.12.2.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad35724c01ad0cb48b3e59728f7841fdc3c7ddcb7ec375683aaf4be75a5ec262
|
|
BLAKE2b-256 checksum How to use checksums |
4fb5d1c889059aea2143ce55bc6ae2b1e054a1c074801cacc6a67431fe43a06f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for sphindexer 0.12.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.
