We now have working wheels being built if [wheel build] is part of the commit since #4, and this forms the basis of our first PyPi release. However, this system currently has a few caveats:
- Builds every Linux based wheel in a single runner (takes around an hour and a half)
Essentially the next steps are to:
- Build "natively" and use the docker images to control what gets built
- Find a smaller subset of interesting builds
- Leave a comment with the artifact link once built
- Make a release notes / changelog document
Why don't we use the trusted release to upload to PyPI directly?
- Because, as I learnt on
asv it is annoying to yank releases
twine upload dist/* is such a trivial step it isn't worth worrying over- Version tagging and auto-releases is nice but it is still nicer to not worry about auto-releases containing bugs! Tags are so easy to remove and test, releases on Pypi much less so.
We now have working wheels being built if
[wheel build]is part of the commit since #4, and this forms the basis of our first PyPi release. However, this system currently has a few caveats:Essentially the next steps are to:
Why don't we use the trusted release to upload to PyPI directly?
asvit is annoying to yank releasestwine upload dist/*is such a trivial step it isn't worth worrying over