Fix CI and semantic-release

[kmpm]

This will...

• test python 3.7
• bump versions
• publish to pypi.

Requires

• GH_TOKENS, PYPI_USERNAME, PYPI_PASSWORD to be set in Travis
• A previous version tag set in git with the format v1.2.3. The v is important.
  The version.py file now points to 9.5.5 so make sure there is a v9.5.5 tag on
  a suitable commit.

This is tested as far as I can get without publishing to the 'live' pypi server. I did a scripted-not-using-sematic-release-upload-to-pypi to test.pypi.org and then removed the project.

You should be the owner of the project on pypi so I let you do the first publish. If you want to do it manually...

python3 setup.py sdist bdist_wheel
twine upload -u <username> -p <password> dist/*

If you wan't to you could add me as a maintainer on the project in pypi after first publish.

[eyeonus]

I sent you a collaborator invite. You can push directly to master. You don't need to PR.

[eyeonus]

Everything that needs to be set up by me is set up.

Travis is failing to build.

$ semantic-release publish
Current version: 9.5.5
Cmd('git') failed due to: exit code(128)
  cmdline: git rev-list ...v9.5.5 --
  stderr: 'fatal: bad revision '...v9.5.5'
'
The command "semantic-release publish" exited with 1.

https://github.com/eyeonus/Trade-Dangerous/releases/tag/v9.5.5

I'll hold off on publishing until the actual build process succeeds.

[kmpm]

semantic-release tries to update v9.5.5 to v9.5.5....

• Did you add the tag before or after push.
  If after then travis might have checked out the code before the tag existed?
• If it was tagged after then what happens if you do a rebuild on the full last build in travis.
  (should be a button on the top somewhere)

[eyeonus]

Before. The tag was added automatically when the branch was merged in.

[eyeonus]

python-semantic-release/python-semantic-release#111

[eyeonus]

https://travis-ci.org/eyeonus/Trade-Dangerous/jobs/490760986