Migration to GitHub actions and readthedocs

[sauln]

• Use GitHub actions for cross-platform testing so we can drop travis and appveyor for testing on linux, mac, and windows.
• Deploy script to auto deploy the package when a new release is cut. (currently deploying to testpypi: https://test.pypi.org/project/ripser/#files)
  • Linux build
  • Windows build
• Readthedocs config so docs get automatically built. (https://ripserpy.readthedocs.io/en/saul-new-deploy-process/)
• Update custom domains to point to readthedocs this will have to happen later and will not be part of the PR process

@ctralie can you confirm the files uploaded to pypi (https://test.pypi.org/project/ripser/#files) are all the one's we need?

[codecov]

Codecov Report

Merging #108 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #108   +/-   ##
=======================================
  Coverage   96.75%   96.75%           
=======================================
  Files           3        3           
  Lines         154      154           
  Branches       26       26           
=======================================
  Hits          149      149           
  Misses          4        4           
  Partials        1        1           

Impacted Files	Coverage Δ
ripser/_version.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 258ad0a...3933463. Read the comment docs.

[bdice]

Hey @sauln I saw you've been pushing on this -- I have some comments that might be helpful. Also you might want to use pyproject.toml for this repository since Cython is a requirement of setup.py. You can see an example here for freud, which has similar requirements: https://github.com/glotzerlab/freud/blob/master/pyproject.toml

pyproject.toml is discussed further here: https://www.python.org/dev/peps/pep-0518/

[bdice]

If possible, I would try to release source distributions and wheel distributions at the same time. I think you could generate source dists and wheels on one platform (e.g. Linux) and then only upload wheels for Windows/other platforms. Here are some example scripts that might be useful.

https://github.com/glotzerlab/freud/blob/master/.circleci/deploy-linux.sh
https://github.com/glotzerlab/signac/blob/master/.circleci/deploy.bash

[sauln]

It looks like pypi doesn't support wheels for linux without using the manylinux package.

[bdice]

Yeah, there are compatibility requirements to make things work on the majority of Linux distros. You can use one of the manylinux container images for deployment if you want.

[sauln]

Previous versions didn't have linux wheels, so I'm fine passing on it right now.

[bdice]

@sauln Looks good to me!