___ _ _ ____
/ | __________(_|_) __ \____ _ ____ __
/ /| | / ___/ ___/ / / / / / __ \| |/_/ / / /
/ ___ |(__ ) /__/ / / /_/ / /_/ /> </ /_/ /
/_/ |_/____/\___/_/_/_____/\____/_/|_|\__, /
/____/
[ Home | What is AsciiDoxy? | Getting started | Reference documentation | Examples | Contributing | Changelog | GitHub ]
AsciiDoxy let's you generate beautiful documentation using the combined power of AsciiDoc and Python. Write your documentation in AsciiDoc format and use Python code and Mako Templates to generate additional content. To top it all off, insert API documentation generated by Doxygen to document your software.
For API documentation, the following languages are currently supported through Doxygen:
- C++
- Java
- Objective-C
- Python (using doxypypy)
- Swift (transcoded from Objective-C only, native support expected in 0.9.x)
- Kotlin (transcoded from Java only, native support expected in 0.9.x)
Other features:
- Collect AsciiDoc files, images, API documentation and other resources from remote servers.
- Generate either a single HTML page or a multipage hierarchy.
- Transcoding: showing how to use elements written in one language in another compatible language.
Get started now!
Want to try out AsciiDoxy together with all the tools it supports? Use our Docker image:
docker run --rm -it silvester747/asciidoxy:latest asciidoxy --help
All you need to get started writing beautiful documentation can be found in our getting started guide.
Credits
Inspiration for creating AsciiDoxy was found in this article by Sy Brand: https://devblogs.microsoft.com/cppblog/clear-functional-c-documentation-with-sphinx-breathe-doxygen-cmake/
Before going public on GitHub, several people inside TomTom contributed to the internal version of AsciiDoxy. Many thanks to:
- Andy Salter
- Arkadiusz Skalski
- Lukasz Glowcyk
- Nebojsa Mrmak
- Niels van der Schans
- Robert Gernert
- Tomasz Maj
The python package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
2 maintainers
Metadata
2 maintainers
Release files for asciidoxy 0.8.7
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 | |
|---|---|---|---|---|
| asciidoxy-0.8.7.tar.gz | 761.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asciidoxy-0.8.7-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 911.7 kB
Release files / asciidoxy-0.8.7.tar.gz
| Download URL | asciidoxy-0.8.7.tar.gz |
|---|---|
| Size | 761.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
194d1a62ab6a30c087dafbfd86ac2d8c209c453daa8d2064be2443d35db53c4e
|
|
BLAKE2b-256 checksum How to use checksums |
9cc114ee24052d9a3558b5fcbac1ae5be7810f70376d7930ba15809a77c3511c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.13
|
Release files / asciidoxy-0.8.7-py2.py3-none-any.whl
| Download URL | asciidoxy-0.8.7-py2.py3-none-any.whl |
|---|---|
| Size | 150.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
722007a878e24fcbf8b1f1f747ea33c7a3bf13f1ab94a356f83cd8477e538831
|
|
BLAKE2b-256 checksum How to use checksums |
fe11153d0b2b11c985a800f47216b5eefebd56a188f72fc4aa82d3968bc680c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.13
|
Security for asciidoxy 0.8.7
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.
