Figure out building and uploading windows wheels to PyPI for releases

[jni]

Installation on windows is not easy when not using conda, see e.g. #2942 #2985. We should figure out how to build release wheels e.g. on AppVeyor so that installing on Windows is easy after release and doesn't rely on a bunch of manual work by the release manager.

[jni]

Here's what appears to be a useful link:

https://packaging.python.org/guides/supporting-windows-using-appveyor/#automatically-uploading-wheels

I would propose adding a twine upload step to the AppVeyor file when we tag a release. Ditto for Travis. I don't know how to manage the credentials and security though. Any suggestions?

[matthew-brett]

You're already using the Rackspace credentials to upload there, for the Linux and macOS wheels, I'd recommend doing the same for the Windows wheels. I've found it very useful to have an intermediate gathering phase before uploading, in case a later wheel build breaks, perhaps requiring a code change. I can set up the Rackspace credentials if you like, for Appveyor. Example here : https://github.com/MacPython/nipy-wheels/blob/master/appveyor.yml

[matthew-brett]

Also - did you see : scikit-image/scikit-image-wheels#3 ?

[hmaarrfk]

Wheels seem to be up on pypi. I guess from scikit-image/scikit-image-wheels#6 PR.

I guess we can close this?

[jni]

@hmaarrfk the current wheels were uploaded manually. Ideally, releasing skimage should be reduced to tagging the right commit on GitHub. There is much work still to do.

[hmaarrfk]

Are OSX and Linux wheels uploaded automatically by travis?

[matthew-brett]

I honestly don't think you should upload the wheels automatically. At the moment, I think you have the standard process used by numpy, scipy, matplotlib etc, where you trigger builds, which upload to Rackspace when done, and there's a final one-liner you need to run manually, to upload these wheels to PyPI. I've found that manual step is very useful, because of a) the inherent unreliability of travis, particularly, and b) the not-negligible likelihood that the builds will find a new problem, requiring further work before release.

[grlee77]

moved back here from discussions, but leaving closed as wheels are now built on GitHub Actions via cibuildwheel and then automatically uploaded to PyPI