Reference#
The factual material, for looking things up rather than reading through.
Generated from the source, so it describes the version you have installed.
What to type at a shell.
What to set, in Python or in a file.
What a word means here, and where the API carries it.
Where a convention or definition came from.
A release, in the few things worth knowing.
A release, one entry per pull request.
If you are deciding what to catch, read tephpy.exceptions. What
tephpy raises about your data — its units, its physical consistency, the
source it came from, the configuration file in force — derives from
TephpyError, so one except clause
covers that subject, and the module sets out the narrower classes for when it
is too broad. Ordinary argument mistakes stay outside the hierarchy and raise
the builtin exceptions instead.
The glossary is worth knowing about before you need it. tephpy’s audience is
scientific software engineers rather than meteorologists, so each entry gives the
concept in one plain sentence and then says how it appears in the package — the
data it involves, its units, and the API that carries it.