Skip to content

Documentation #5

@Holiverh

Description

@Holiverh

There is okayish docstring coverage but it could be much better.

Sphinx is the way to go. Perhaps take a look at hooking it up to readthedocs as well. Ideally the documentation should cover everything with a few examples of intended usage patterns.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions