sphinxcontrib-getstart-sphinx
sphinxcontrib-getstart-sphinx is a collection of Sphinx extensions to build Sphinxをはじめよう 第2版 (Getting Started with Sphinx 2nd Edition).
This package provides following extensions:
- sphinxcontrib.getstart_sphinx.better_docref
Append section numbers to each :doc: references.
- sphinxcontrib.getstart_sphinx.column
Add column directive to note columns.
- sphinxcontrib.getstart_sphinx.footnote_relocator
Move footnote definitions to the bottom of each sections.
- sphinxcontrib.getstart_sphinx.glossary_decorator
Make terms of glossaries bold.
- sphinxcontrib.getstart_sphinx.oreilly_review_table
Convert tables in Re:VIEW output to original notation for O’Reilly Japan internal tools.
Usage
To enable all extensions in this package, please add sphinxcontrib.getstart_sphinx to your extensions list in conf.py:
extensions = ['sphinxcontrib.getstart_sphinx']
If you want to enable specific extensions individually, please add its name to the list like bollow:
extensions = ['sphinxcontrib.getstart_sphinx.better_docref',
'sphinxcontrib.getstart_sphinx.footnote_relocator']
Directives
You can use following directives:
- column
A directive to note a column. It takes a title of column as an argument, and also takes body of column as content block.
Example:
.. column:: SphinxとPythonのバージョンの関係 バージョン1.5以降、Sphinxを動作させるには2.7もしくは3.4以上の Pythonが必要です。 そのため、古いPythonがインストールされるCentOS 6.x系などのディスト リビューションでは、最新のSphinxが利用できません。
Settings
You can configure following settings to arrange the behavior of the extension.
- section_numbers:
A dict for mapping docname to section number text. This is used by better_docref extension to build a link title for document reference.
Example:
section_numbers = { 'ch01': '第1章', 'ch02': '第2章', 'ch03': '第3章', 'ch04': '第4章', 'ch05': '第5章', 'ch06': '第6章', 'appendix/references': '付録A', 'appendix/builders': '付録B', 'appendix/quickstart': '付録C', 'appendix/texlive': '付録D', 'appendix/make_sh': '付録E', 'appendix/markdown': '付録F', 'appendix/community': '付録G', }
Metadata
Release files for sphinxcontrib-getstart-sphinx 1.2.0
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 | |
|---|---|---|---|---|
| sphinxcontrib-getstart-sphinx-1.2.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinxcontrib_getstart_sphinx-1.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 15.7 kB
Release files / sphinxcontrib-getstart-sphinx-1.2.0.tar.gz
| Download URL | sphinxcontrib-getstart-sphinx-1.2.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2bd1e02db6bcde66208c8df6d3a2a4efb15ba7a6e8a65ad74ccbd640b012064
|
|
BLAKE2b-256 checksum How to use checksums |
ad83bbcc25caa798792e0ebd55b839ccb97ff78587f5e9271ea4c5fb2ff25190
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.8
|
Release files / sphinxcontrib_getstart_sphinx-1.2.0-py2.py3-none-any.whl
| Download URL | sphinxcontrib_getstart_sphinx-1.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
cd849df08be163d27c45ff9913a7bf6a5f3f1d0d9e5fd9b92ca81e9b88d6609e
|
|
BLAKE2b-256 checksum How to use checksums |
108eaf2a33510b507335b59cc3bd40a8865d336a4e72d63441d5f68eac4b6725
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.8
|
Security for sphinxcontrib-getstart-sphinx 1.2.0
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.