Created by Stephen McDonald
Introduction
Do you have smaller Python projects that only need a README file for documentation? Want to host your README on Read The Docs?
sphinx-me is a BSD licensed tool that will create a Sphinx documentation shell for your project and include the README file as the documentation index. It handles extracting the required meta data such as the project name, author and version from your project for use in your Sphinx docs.
Once you use sphinx-me to build your Sphinx docs, you can then add your project to the Read The Docs site and have your project’s README hosted with an attractive Sphinx documentation theme.
Installation
The easiest way to install sphinx-me is directly from PyPI using pip or setuptools by running the respective command below:
$ pip install -U sphinx-me
or:
$ easy_install -U sphinx-me
Otherwise you can download sphinx-me and install it directly from source:
$ python setup.py install
Running
sphinx-me will be installed as a system-wide script that can be run from the command line while in your project’s root directory:
$ sphinx-me
When run in your project’s directory, it will create a docs directory with two files, the Sphinx conf.py module, and an index.rst file which will include your project’s README.
The conf.py module calls a setup function from sphinx-me that sets up the minimum required settings for your Sphinx docs.
project - the directory name of your project is used.
version - retrieved from the version arg of your setup.py script, or your package’s __version__ attribute.
copyright - retrieved from the author arg of your setup.py script, or your package’s __author__ attribute.
Running this process will also perform an initial sphinx-build inside your project’s docs/build directory. Subsequent builds after making changes to your README can be performed by running sphinx-me again, or by using the regular sphinx-build command.
Hosting on Read The Docs
When hosting your sphinx-me generated docs on Read The Docs, you must ensure you check the Use virtualenv option and specify sphinx-me as a requirement in either your setup.py script, or in a pip requirements file that you’ll need to also specify in the Requirements file field for your project on Read The Docs.
Metadata
Release files for sphinx-me 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-me-0.3.tar.gz | 5.7 kB | Without provenance | Details for sphinx-me-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_me-0.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for sphinx_me-0.3-py2.py3-none-any.whl |
Total release size: 13.2 kB
Release files / sphinx-me-0.3.tar.gz
| Download URL | sphinx-me-0.3.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98bef823a4053ca1ccbbe2322bd855a3c5e98797c50bcfeeb630fe11c47d5f1a
|
|
BLAKE2b-256 checksum How to use checksums |
1505fa421fa08ab98342b71371117af7197ff130ef6dc7d7646c60a91e9d7eeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / sphinx_me-0.3-py2.py3-none-any.whl
| Download URL | sphinx_me-0.3-py2.py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2c67a6bbf9d60631a84b687f0bafbfe2cb16e2663deee28ce03d5f07c7d89807
|
|
BLAKE2b-256 checksum How to use checksums |
d05419bc2492a652450bad1faa1de5f4d722bd6965ab2ad5f2c5f3ef9304a930
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sphinx-me 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.