##############################################
.. image:: https://img.shields.io/pypi/v/lydoc.svg?maxAge=2592000
:target: https://pypi.python.org/pypi/lydoc
:alt: PyPI Package
.. image:: http://readthedocs.org/projects/lydoc/badge/?version=latest
:target: http://lydoc.readthedocs.io/en/latest/?badge=latest
:alt: Documentation Status
.. image:: https://travis-ci.org/Cecca/lydoc.svg?branch=master
:target: https://travis-ci.org/Cecca/lydoc
:alt: Continuous Integration
..
The marker below is used to tell Sphinx where to start
to include the README file into the main documentation
.. inclusion-marker
Lydoc is a software that looks for documentation comments in `GNU
Lilypond`_ source files, and outputs API documentation in a variety of
formats.
-----------------------------------------------------------------------
Installation
============
Lydoc works with both Python 2 (version 2.7 is supported) and Python 3
(versions 3.3, 3.4, and 3.5). You can install it in several ways.
>From source
-----------
Clone the repository somewhere on your machine. To install, run from
the root directory of the project::
python setup.py install
which will install the ``lydoc`` executable, while fetching all the
necessary dependencies in the process. To upgrade, just pull the
latest changes and run the above command again.
>From PyPI
---------
Lydoc is also available on the Python Package Index. You can install
it with this single command::
pip install --user lydoc
I recommend running the above command with the ``--user`` option so
not to mess with system packages. If you omit the ``--user`` argument,
you might require administration privileges, depending on you
machine's configuration.
To upgrade, it is sufficient to run the following command::
pip install --user --upgrade lydoc
Very quick start
================
Just run the following command::
lydoc -o api.rst file.ly
to collect documentation from ``file.ly`` and write a ``api.rst`` text
file formatted with `reStructuredText`_.
Quick start
===========
Lydoc will look for documentation comments in the given file or
directory. In the latter case, it will parse all ``.ly`` and ``.ily``
files, recursively. A documentation comment looks like a standard
Lilypond block comment, with a slightly different opening::
%{!
% I am a documentation comment :-)
%}
someFunction =
#(define-music-function ...)
Note the ``!`` character after the opening of the comment: that's the
character that Lydoc uses to distinguish between normal block comments
and documentation ones.
So, to extract the documentation from a single file, the command line
is the following::
lydoc file.ly
This will output some logging information to standard error, and the
collected documentation on standard output, as a stream of JSON
objects, one per line. This is useful to pipe the output of Lydoc to
some other program, in a machine-friendly format.
However, we are humans, not machines, hence we might want to generate
something more readable, like a file in some lightweight markup
language. You have some options:
`Markdown`_
Arguably the most widespread lightweight markup language::
lydoc -o api.md file.ly
`reStructuredText`_
The markup language used by the powerful `Sphinx`_
documentation generator::
lydoc -o api.rst file.ly
To generate API documentation for a single lilypond file in
`reStructuredText`_ format::
lydoc -o api.rst file.ly
or in `Markdown`_::
lydoc -o api.md file.ly
For more detailed usage instructions, head to the :doc:`/user-manual`
page.
.. _`GNU Lilypond`: http://lilypond.org/
.. _reStructuredText: http://www.sphinx-doc.org/en/stable/rest.html
.. _Markdown: http://daringfireball.net/projects/markdown/
.. _Sphinx: http://www.sphinx-doc.org/en/stable/index.html
Metadata
Release files for lydoc 0.1.1
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 |
|---|---|---|---|---|
| lydoc-0.1.1.tar.gz | 22.8 kB | Without provenance | Details for lydoc-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lydoc-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for lydoc-0.1.1-py2.py3-none-any.whl |
Total release size: 36.8 kB
Release files / lydoc-0.1.1.tar.gz
| Download URL | lydoc-0.1.1.tar.gz |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b20ed39c7f06c3278372f06012c7c95df11592cce851cb555702c0a5899c4c72
|
|
BLAKE2b-256 checksum How to use checksums |
7fb2774cab34795868241df9a7bbf20c74ab42c49bb99c4c0c50719eeadbf885
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / lydoc-0.1.1-py2.py3-none-any.whl
| Download URL | lydoc-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
571fbfe6df9548317ad42b14ad850b4f4c708659d2b6f218ca951fc4005e2cb7
|
|
BLAKE2b-256 checksum How to use checksums |
af6549464c73f18a51c0d07cef18c498e2a907b895be62ce55297fdf2bd83454
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lydoc 0.1.1
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.