Sphinx Comments
Add comments and annotation functionality to your Sphinx website.
Currently, these commenting engines are supported:
- Hypothes.is provides a web overlay that allows you to annotate and comment collaboratively.
- utteranc.es is a web commenting system that uses GitHub Issues to store and manage comments.
dokie.liis an open source commenting and annotation overlay built on web standards.
For examples of each service, as well as instructions for how to activate it,
see the sphinx-comments documentation.
Contribute to Sphinx Comments
Sphinx Comments follows the Executable Books contributing guide.
Install for development
To install sphinx-comments for development, take the following steps:
git clone https://github.com/executablebooks/sphinx-comments
cd sphinx-comments
pip install -e .[testing,sphinx]
This will install the dependencies needed for development and testing.
Repository structure
Sphinx Comments is a lightweight Sphinx extension that activates several Javascript libraries for use within Sphinx. All of its functionality is contained in sphinx_comments/__init__.py.
As a general rule, Sphinx Comments tries to be as lightweight as possible. It simply:
- Loads Javscript libraries for web commenting and annotation platforms
- Provides a configuration layer for platforms that support it
Note that some of these platforms cannot be activated at the same time, users will need to choose one or the other.
Some of the annotation platforms require more complex setup - for example, utteranc.es requires its script to be placed in a specific location on the page, and so sphinx-comments will place it directly in the doctree of the page (underneath the content).
Metadata
Release files for sphinx-comments 0.0.3
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 |
|---|---|---|---|---|
| sphinx-comments-0.0.3.tar.gz | 8.0 kB | Without provenance | Details for sphinx-comments-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_comments-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for sphinx_comments-0.0.3-py3-none-any.whl |
Total release size: 12.6 kB
Release files / sphinx-comments-0.0.3.tar.gz
| Download URL | sphinx-comments-0.0.3.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00170afff27019fad08e421da1ae49c681831fb2759786f07c826e89ac94cf21
|
|
BLAKE2b-256 checksum How to use checksums |
c0755bbf29e83eaf79843180cf424d0d550bda14a1792ca51dcf79daa065ba93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.3.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.7.8
|
Release files / sphinx_comments-0.0.3-py3-none-any.whl
| Download URL | sphinx_comments-0.0.3-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e879b4e9bfa641467f83e3441ac4629225fc57c29995177d043252530c21d00
|
|
BLAKE2b-256 checksum How to use checksums |
2697a5c39f619375d4f81d5422377fb027075898efa6b6202c1ccf1e5bb38a32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.3.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.7.8
|
Security for sphinx-comments 0.0.3
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.