Following comments on 5d21c69, we should simplify the code in setup.py that generates the version string that labels an installation of Slycot. This is somewhat nontrivial because, for non-release commits, it is useful to include the commit hash in the version string.
Two proposals have been made thus far:
- use versioneer (5d21c69)
- use make_version.py from
python-control (5d21c69#commitcomment-20885735)
Interestingly, this is a perennial issue in the development of Python packages that have change history tracked in Git. Slycot requires compilation of FORTRAN code, so NumPy should be a good first reference regarding labeling built binary packages.
Following comments on 5d21c69, we should simplify the code in setup.py that generates the version string that labels an installation of Slycot. This is somewhat nontrivial because, for non-release commits, it is useful to include the commit hash in the version string.
Two proposals have been made thus far:
python-control(5d21c69#commitcomment-20885735)Interestingly, this is a perennial issue in the development of Python packages that have change history tracked in Git. Slycot requires compilation of FORTRAN code, so NumPy should be a good first reference regarding labeling built binary packages.