Closed petrelharp closed 3 months ago
0.2 seems right - I guess we can then plan for 0.3 as the version that converts the demographic models in the catalog to demes (with some code breakage, probably)?
git push; git push --tags
python3 setup.py sdist bdist_wheel
twine upload dist/FILES_TO_UPLOAD
"The key things I checked were that the version number is correct, the SHA sum has changed, and that the build number is reset to zero. Any other problems should be caught by the automated build system."
Post-release:
Reference: https://packaging.python.org/tutorials/packaging-projects/, https://github.com/tskit-dev/pyslim/issues/292
- [ ] make sure you're on main
- [ ] increment the version in _version.py [NP: doesn't exist?]
- [ ] update CHANGELOG
- [ ] commit and tag
- [ ] update tags on github with
git push; git push --tags
- [ ] upload to pypi:
FYI, stdpopsim is using setuptools_scm
to determine the version. So, when you build the package with something like python setup.py build
(or using non-deprecated build tools pip install build; python -m build
), then the stdpopsim/_version.py
file will be created. This means you need to create the tag, then build, before the appropriate version will be visible.
Also, we should change from using setup.py to using pyproject.toml and setup.cfg, following current best practices for Python packages (setup.py is deprecated).
Yes, using setuptools_scm means you do it in slightly different order. I find this simplest:
- python3 -m twine upload [stuff]
You're still uploading to pypi manually, like a barbarian? :P
Adds the personal touch for grass-fed artisanal packages
We have done this.
TODO (is 0.2 the next number? the last one was 0.1.2)