sphinxcontrib-vcs
sphinxcontrib-vcs provides showing commit history in version control system.
Setup
$ pip install sphinxcontrib-vcs
Usage
Add 'sphinxcontrib.vcs' as extensions into conf.py.
$ vi conf.py
extensions = ['sphinxcontrib.vcs']
Then, repository directives are available as follows.
Git
.. git::
:number_of_revisions: 20
:with_ref_url:
:include_diff:
For more information have a look at the documentation.
Acknowledgments
sphinxcontrib-vcs is inspired from the sphinx-git.
ChangeLog
0.3.0 (2020-04-19)
- drop Python 3.5 support
- add type annotation and modules reference
0.2.2 (2019-11-06)
- fix packaging issue: cannot import sphinxcontrib.repository
0.2.1 (2019-08-04)
- fix wrong Docutils DTD list_item node thanks to amedama41
0.2.0 (2018-11-17)
- drop Python 2.7 support and mercurial feature
- support internal git repository such as GitHub Enterprise
0.1.0 (2016-09-06)
- first release
Metadata
Release files for sphinxcontrib-vcs 0.3.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 | Actions |
|---|---|---|---|---|
| sphinxcontrib-vcs-0.3.0.tar.gz | 13.0 kB | Without provenance | Details for sphinxcontrib-vcs-0.3.0.tar.gz |
Release files / sphinxcontrib-vcs-0.3.0.tar.gz
| Download URL | sphinxcontrib-vcs-0.3.0.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e38b1d568176f60b2af780d6b5da23785d7db16480d921bbdd6a25708d5de8dc
|
|
BLAKE2b-256 checksum How to use checksums |
fe0ffae668c725472f2920b0234f1c8f08d849fdddbfe5c3e8e1415e2a3159c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.1
|
Security for sphinxcontrib-vcs 0.3.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.