Repository navigation
0.2.0
A file now states a specification, or spec. A model is a spec with
data attached, which an engine builds and a solver takes. mathspec holds specs
only. The API, the messages and the docs use the two words in these senses
(glossary).
This release breaks three things:
- The first parameter of
to_spec,advice,typeset,typeset_declaration,
to_latex,to_typstandto_markdownisspec, notmodel. A call that
passesmodel=by keyword fails. A positional call works as before. - The module
mathspec.modelis nowmathspec.spec.from mathspec import Spec
works as before. - Error and advice messages say "spec" where they said "model". A test that
matches the old text fails.
The pull requests in this release:
- feat!: what a file states is called a spec, the functions that read one take it as spec, and model means a spec with data (#721)
- docs: the README and the docs home page say that spec is short for specification (#724)
- fix(docs): the Python API pages link every name a docstring cites, and show advice as the function it is (#720)