Strict python minimum version for install (Issue #112) and auto-deployment via actions

[IAlibay]

Add python_requires, drops universal entry for wheel generation (note we probably should clean that out of the core repo's setup.cfg too...)

To do:

• test that this works on testpypi (@orbeckst could you give me access on both pypi and testpypi? my user name is IAlibay on both)
• test that this works for wheel generation using build

[codecov]

Codecov Report

Merging #113 (5e1fe04) into master (a15397d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   87.56%   87.56%           
=======================================
  Files           5        5           
  Lines         748      748           
  Branches      133      133           
=======================================
  Hits          655      655           
  Misses         56       56           
  Partials       37       37           

---

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 a15397d...5e1fe04. Read the comment docs.

[IAlibay]

pypa has some really good docs on this, it was a surprising experience: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

This will run a build runner every time we push/PR, and also whenever there's a release. If we push a new tag it will upload the build to testpypi for us to check before a release, if we pusblish a release it'll be automatically pushed to pypi.

What needs to be done here is:

1. Uploading the relevant github secret API tokens for testpypi and pypi.
2. Checking that the testpypi upload works (create a fake tag for an alpha version of 1.0.1 upload it and then delete the tag?)
3. Checking that the pypi upload works on publication of the next release.

[orbeckst]

This looks good (as in the PyPI docs).

I don't have a TestPyPI account. Can you set up the TestPyPI repo and the secrets?

[orbeckst]

@IAlibay I invited you as owner on PyPi for gdf

[IAlibay]

@IAlibay I invited you as owner on PyPi for gdf

thanks, is there a testpypi project too?

[orbeckst]

Will you be able to check the new workflow once you have accepted ownership of gdf or do you need me to do something here?

[orbeckst]

No, there's no testpypi.

[IAlibay]

Will you be able to check the new workflow once you have accepted ownership of gdf or do you need me to do something here?

Yeah I'll need to create a testpypi version but that should be fine

[orbeckst]

LGTM, as far as I can tell. Thank you for modernizing!

[orbeckst]

Should there be a "Fixes" that indicates that 1.0.0 could fail to install if it was incorrectly attempted in a 2.7 or <3.8 environment?

[IAlibay]

Sure I can swap that first bullet point to a fixes entry.

[orbeckst]

This looks good (as in the PyPI docs).

I don't have a TestPyPI account. Can you set up the TestPyPI repo and the secrets?

[IAlibay]

Ok I've removed the requirement to review the build action because otherwise this will never end. Everything seems to work right now, I just need to create the 1.0.1 release tag and see if testpypi likes it.