In #2018 the theory db utils are separated into the data package, like this external programs can easily depend not only on the theory cards but also in the definition of the theory.
My suggestion is something very simple, just a dataclass declaring the field, with several which will mandatory for everyone and some that will be optional (and for which can either set a default here or set None and let the decision to each program).
class _TheoryCard:
ID: int
PTO: int
FNS: str
DAMP: int
IC: int
ModEv: str
XIR: float
XIF: float
NfFF: int
In #2018 the theory db utils are separated into the data package, like this external programs can easily depend not only on the theory cards but also in the definition of the theory.
My suggestion is something very simple, just a dataclass declaring the field, with several which will mandatory for everyone and some that will be optional (and for which can either set a default here or set
Noneand let the decision to each program).