Codecov Report

Merging #430 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #430   +/-   ##
=======================================
  Coverage   90.52%   90.52%           
=======================================
  Files          50       50           
  Lines        6973     6973           
  Branches     1328     1328           
=======================================
  Hits         6312     6312           
  Misses        502      502           
  Partials      159      159

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 af19281...98ff5ca. Read the comment docs.

Deploy non-tagged builds to Test PyPI

Perhaps stupid question, "Test PyPI"?

It's "a separate instance of the Python Package Index that allows you to try distribution tools and processes without affecting the real index".

https://test.pypi.org/

I find it useful to deploy to TestPyPI on untagged merges to master. That way, it's actually testing the release process and machinery, to give confidence that tagged builds deploy to production PyPI.

For example, I have it set up in https://github.com/hugovk/pypistats, which also uses setuptools_scm, so the dev version number automatically updates, and so a new upload can go to TestPyPI for each merge.

Another benefit is it creates WIP builds which people could use for testing in between releases.

More info on TestPyPI:
https://packaging.python.org/guides/using-testpypi/