Prepare for new colout version

[stdedos]

Because there is a weird v0.11 tag, we pick the next version v0.12.0,
instead of the "real" next version aka v0.7.0

This project is considered to use Semantic Versioning (https://semver.org/)
(https://semver.org/spec/v2.0.0.html as of now)

Python versioning updates:

• Unify that package is offered for >=Python3.5
  2.7 support was dropped in dab5555,
  and <3.5 versions do not exist in https://devguide.python.org/#status-of-python-branches as of committing time

• Add some classifiers (YMMV, my first pip package)

• Add some bare-bones tox configuration (YMMV, my first tox interaction)

• Add packages required for packaging/deployment in requirements-build.txt

• README.md is not required to be packaged anymore - it is read at install time

  • Fix Content-Type for PyPI

• Update README.md:

  • Reorder installation options (pip > pipsi > ppa)
  • Hard wrap at 100 chars for "meaningful" offences.
  • Add myself as maintainer
  • Remove escapes that don't make sense in CommonMark
    (GFM, as project is hosted in Github)
  • Fix typos

• Add a more complete .gitignore file

[stdedos]

@nojhan "please review" - pending pypi/support#418 resolved and afterwards a test to https://test.pypi.org/

[stdedos]

Should be ready. Please review & try to install it from https://test.pypi.org/project/colout/0.12.0rc1/

---

After accepting/merging, please remember to create and push an annotated tag:

$ git pull
$ git tag -a v0.12.0 -m "(I cannot think of a message. 'Release v0.12.0'? More / Less? Do you want to write a changelog? GPG sign this?)"
$ git push --tags

So I can create the matching official PyPI release. (Or give me write access to your copy of the repository 😄)

[nojhan]

Merged, thanks!

[stdedos]

Are you sure you merged this?

And the v0.12.0 git tag you created is in a wrong commit 😃