Automate the release procedure.

[rainwoodman]

The instructions are at:

https://docs.travis-ci.com/user/deployment/pypi/

You can refer to the example in bigfile:

https://github.com/rainwoodman/bigfile/blob/1a2d05977fc8edebd8ddf9e81fdb97648596266d/.travis.yml#L47

The basic idea is run the auto deployment on tags and builds that ends with .0. Then when you do

git tag 1.0.0
git push --tags

Then very first build in the build matrix will run auto deployment and create a release on PyPI. In bigfile I added a script (check_tag.sh) to assert the tag agrees with the version number before sending the release to PyPI, since it is a common mistake the claimed version in the package disagrees with the tag name.

You do need to compute your encrypted pypi password via the travis CLI command. The procedure is described in their guide (I don't think they have a web interface for that).

[rainwoodman]

This is blocking bccp/nbodykit#579, which appears to require the new version of mcfit, which is not yet released on PyPI nor tagged on github.

[eelregit]

Thanks! I think fixed that after CI failed and now there is a new version.

I will spend some time to understand all the automation stuff.
For now, do you know how to simply restart travis in bccp/nbodykit#579?

[rainwoodman]

You can probably force push with a trivial change to restart th build. I can also manually restart it from the travis site.