setup.py: Add classifiers and python_requires

[vilhelmprytz]

Description of new feature, or changes

I have added a list of classifiers to the setup.py. This is mostly metadata but will make it easier to see what versions are supported. Also added python_requires which blocks older versions. I have assumed that Halo does not support versions older than 3.4. If this is incorrect it should be fairly easily adjustable.

Checklist

• [x] Your branch is up-to-date with the base branch
• [x] You've included at least one test if this is a new feature
• [x] All tests are passing

Related Issues and Discussions

Currently, Halo shows up as "not python 3 compatible" on sites like pyup.io. I am aiming to solve this problem.

People to notify

N/A

[vilhelmprytz]

Is the Travis check misconfigured here? It hasn't been triggered at all.

[vilhelmprytz]

Any news regarding this?

[coveralls]

Pull Request Test Coverage Report for Build 444

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 83.036%

---

Totals
Change from base Build 440:	0.0%
Covered Lines:	302
Relevant Lines:	356

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 443

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 83.036%

---

Totals
Change from base Build 440:	0.0%
Covered Lines:	302
Relevant Lines:	356

---

💛 - Coveralls

[manrajgrover]

Thanks @vilhelmprytz !

[vilhelmprytz]

@manrajgrover Have you pushed to PyPI yet? You should use GitHub releases so that you can via your CI automatically build and push to PyPI upon release :+1:

[manrajgrover]

I've made a release on PyPI.

https://pypi.org/project/halo/0.0.31/

I haven't explored CI for releases. I'll have a look for future releases.

Thanks again!