Automate packaging

[ZedThree]

Closes #324 Fixes #80

This requires a PyPI API token to be added as a secret named PYPI_DEPLOYMENT_TOKEN to this repo. Once that's been added, every new GitHub release will automatically trigger building a package and uploading to PyPI.

This now sets the version from the latest git tag using setuptools_scm, so for instance, the latest commit on this branch is:

$  python -c "import fparser; print(fparser.__version__)"
0.0.15.dev4+g877584c

Note that this version is only updated on pip install, even for editable installs.

Also, I note that fparser2 --version doesn't work, I suspect because you're using optparse. I'm happy to look at upgrading to argparse which would give you that for free.

[ZedThree]

The tests are failing because setuptools_scm doesn't support python 2.7 or 3.5, so this needs to wait for #322

[arporter]

I've added a suitable secret. We just need @rupertford to review #322 now ;-)

[codecov[bot]]

Codecov Report

Merging #327 (14a7787) into master (8e8ae1d) will decrease coverage by 0.01%. The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master     #327      +/-   ##
==========================================
- Coverage   91.27%   91.25%   -0.02%     
==========================================
  Files          36       36              
  Lines       12994    13004      +10     
==========================================
+ Hits        11860    11867       +7     
- Misses       1134     1137       +3     

Impacted Files	Coverage Δ
src/fparser/__init__.py	83.33% <72.72%> (-16.67%)	:arrow_down:

---

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 8e8ae1d...14a7787. Read the comment docs.

[arporter]

Hi @ZedThree, this one's next on my list now. Would you mind bringing it up-to-date with master and removing the six dependency?

[arporter]

We're consisdering making a new release and would like to get this on before then. @ZedThree, do you have time to continue with this or would you like one of us to take it on?

[arporter]

The work in this PR has been moved over to #391.