On 1 November 2016 at 12:19, Nick Coghlan
It isn't that simple, as what you really want to automate is the *release process*, where you upload an sdist, and the wheels *just happen* for:
- the Python versions you want to support (e.g 2.7, 3.4, 3.5) - the platforms you want to support (typically x86_64 for Windows, Mac OS X, manylinux1, and maybe 32 bit Windows as well)
Adding a new Python release or a new platform to the build configuration is currently an activity that requires per-project work when in theory a build service could just add it automatically based on when new releases happen.
Ah. If you're looking for automated publication on PyPI (or alternatively, creation and maintenance of a secondary index for wheels) then yes, that's a much bigger piece of work. Paul